Triple
T12680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California quail |
E255
|
entity |
| Predicate | hasDistinctiveFeature |
P182
|
FINISHED |
| Object | forward-curving head plume |
—
|
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: forward-curving head plume | Statement: [California quail, hasDistinctiveFeature, forward-curving head plume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctiveFeature Context triple: [California quail, hasDistinctiveFeature, forward-curving head plume]
-
A.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
D.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
E.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a243abb2ec8190937365e5ecec52ad |
completed | Feb. 28, 2026, 1:23 a.m. |
| PD | Predicate disambiguation | batch_69a23fe9470c8190918a6ca1df168646 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.