Triple
T26708368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turnagra |
E673340
|
entity |
| Predicate | historicallyPlacedInFamily |
P154668
|
FINISHED |
| Object | Oriolidae |
—
|
NE NERFINISHED |
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: Oriolidae | Statement: [Turnagra, historicallyPlacedInFamily, Oriolidae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPlacedInFamily Context triple: [Turnagra, historicallyPlacedInFamily, Oriolidae]
-
A.
historicalFamily
chosen
Indicates a familial relationship that existed between entities in the past, regardless of whether it still holds in the present.
-
B.
heldByFamilySince
Indicates that something has been continuously possessed or owned by the same family from a certain point in time.
-
C.
historicalFamilyPlacement
Indicates the recorded arrangement or position of an individual within a family structure at some point in the past.
-
D.
chronologyWithinFamily
Indicates that one family-related event or state occurs within the temporal span defined by another family-related event or state.
-
E.
hasGenealogicalSignificance
Indicates that something holds importance or relevance within a genealogical or family-lineage context.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 27, 2026, 3:35 a.m.