Triple
T16615373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osmeridae |
E403682
|
entity |
| Predicate | lifeHistoryTrait |
P40326
|
FINISHED |
| Object | some species 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: some species anadromous | Statement: [Osmeridae, lifeHistoryTrait, some species anadromous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeHistoryTrait Context triple: [Osmeridae, lifeHistoryTrait, some species anadromous]
-
A.
lifeCharacteristic
Indicates that an entity possesses a particular trait, feature, or quality relevant to its life or living state.
-
B.
lifePeriod
Indicates the span of time during which an entity exists, is active, or is valid.
-
C.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
D.
lifeDetails
Indicates that additional information or specific aspects about an entity’s life (such as background, experiences, or personal history) are being described.
-
E.
biologicalCharacteristic
chosen
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3609935a88190baa56f3a42b2ecd1 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.