Triple
T2447515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neognathae |
E53627
|
entity |
| Predicate | hasLivingRepresentatives |
P33585
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Neognathae, hasLivingRepresentatives, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivingRepresentatives Context triple: [Neognathae, hasLivingRepresentatives, true]
-
A.
hasRepresentativeBody
Indicates that an entity is associated with or governed by a specific representative body that acts or decides on its behalf.
-
B.
hasExtantMembers
chosen
Indicates that the referenced group, category, or lineage currently has living or existing members.
-
C.
hasLifeSenators
Indicates that certain individuals hold the status or role of life senators within a given political or organizational context.
-
D.
hasParliamentMembers
Indicates that a governing body or political entity possesses or is represented by one or more members in a parliament.
-
E.
hasElectoralRepresentation
Indicates that one entity is represented in an electoral body or decision-making institution by another entity (such as a representative, party, or delegation).
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:43 p.m.