Triple
T4038900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aburria |
E83893
|
entity |
| Predicate | firstDescriptionContext |
P53747
|
FINISHED |
| Object | ornithology |
—
|
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: ornithology | Statement: [Aburria, firstDescriptionContext, ornithology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDescriptionContext Context triple: [Aburria, firstDescriptionContext, ornithology]
-
A.
firstStageDescription
Indicates that the value provides a textual explanation or summary of the initial or earliest stage in a multi-stage process or sequence.
-
B.
firstDescribedAs
Indicates the original way or terms in which something was initially characterized, named, or documented.
-
C.
firstPublicationContext
Indicates the original context or setting (such as venue, medium, or circumstance) in which something was first published.
-
D.
firstOfficialReleaseContext
Indicates the context or setting (such as region, platform, or format) in which something was first officially released.
-
E.
firstScoreDescription
Indicates the textual description associated with an entity’s first or initial score.
- F. None of above. chosen
Provenance (4 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb37e24c81908d6357ab8ba5388d |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef98ed84c81909dc86097df4afd4f |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:37 p.m.