Triple
T27881981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epimachus |
E705112
|
entity |
| Predicate | displayTrait |
P41649
|
FINISHED |
| Object | males have long decurved bills |
—
|
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: males have long decurved bills | Statement: [Epimachus, displayTrait, males have long decurved bills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayTrait Context triple: [Epimachus, displayTrait, males have long decurved bills]
-
A.
displayType
Indicates the manner or format in which something is presented, shown, or rendered.
-
B.
distinguishingTrait
Indicates that a particular characteristic or feature uniquely differentiates one entity from another.
-
C.
displaysFeature
chosen
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
D.
portrayalFeature
Indicates that one entity serves as a characteristic, aspect, or attribute highlighted in the depiction or representation of another entity.
-
E.
notableTraitOnStage
Indicates that an entity is characterized by a distinctive or noteworthy trait specifically in the context of performing or appearing on stage.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 6:30 p.m.