Triple
T8652573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sockeye salmon |
E205134
|
entity |
| Predicate | hasLifeHistoryType |
P80089
|
FINISHED |
| Object | anadromous |
—
|
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: anadromous | Statement: [Sockeye salmon, hasLifeHistoryType, anadromous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLifeHistoryType Context triple: [Sockeye salmon, hasLifeHistoryType, anadromous]
-
A.
hasLifeHistoryStrategy
chosen
Indicates a relationship where an organism is associated with a particular life history strategy, describing how it allocates resources to growth, reproduction, and survival over its lifespan.
-
B.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
C.
hasHistoricResourceType
Indicates that an entity is associated with a particular category or type of historic resource.
-
D.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
E.
hasAncestralEvent
Indicates that an entity is associated with a past ancestral occurrence or event in its lineage.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc484051b48190b1d0cc63426c204d |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.