Triple
T26868637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eufalconimorphae |
E676542
|
entity |
| Predicate | isMajorLineageWithin |
P41814
|
FINISHED |
| Object | Australaves |
—
|
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: Australaves | Statement: [Eufalconimorphae, isMajorLineageWithin, Australaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorLineageWithin Context triple: [Eufalconimorphae, isMajorLineageWithin, Australaves]
-
A.
isLineageType
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
-
B.
isDescendantLineOf
Indicates that one entity is connected to another through a direct or indirect line of descent, such as child, grandchild, or further generational lineage.
-
C.
isMajorLineOf
chosen
Indicates that one entity is a primary or principal route, branch, or component within the structure or network represented by the other entity.
-
D.
hasLineageRole
Indicates a relationship where an entity holds a specific role or function within a lineage, ancestry, or genealogical chain.
-
E.
hasLineageMember
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 5:30 a.m.