Triple
T32561578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Littorinidae |
E832238
|
entity |
| Predicate | lifeZone |
P2160
|
FINISHED |
| Object | littoral zone |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: littoral zone | Statement: [Littorinidae, lifeZone, littoral zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeZone Context triple: [Littorinidae, lifeZone, littoral zone]
-
A.
lifeDomain
Indicates the broad biological or existential category or realm within which an entity’s life or living characteristics are classified.
-
B.
zone
chosen
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
C.
lifeCycle
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
-
D.
lifeSpanLocation
Indicates the place or geographic context in which an entity’s lifespan occurs or is associated.
-
E.
lifeSituation
Indicates the general circumstances, conditions, or context in which an entity’s life currently exists or unfolds.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c6084a348190a1b644c398d91589 |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.