Triple
T10052379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coho salmon |
E208777
|
entity |
| Predicate | hasLifeCycleType |
P3733
|
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: [Coho salmon, hasLifeCycleType, anadromous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLifeCycleType Context triple: [Coho salmon, hasLifeCycleType, anadromous]
-
A.
hasLevelType
Indicates that an entity is associated with a specific type or category of level (e.g., difficulty, hierarchy, or stage).
-
B.
hasStageType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
C.
hasRuntimeType
Indicates that an entity is of, or conforms to, a specific type when evaluated at runtime rather than at compile time.
-
D.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
E.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf9135bc8190a48a2e5cbafca0cd |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.