Triple
T796392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nēnē |
E17031
|
entity |
| Predicate | plumageDescription |
P4572
|
FINISHED |
| Object | buff-colored neck with black head and face |
—
|
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: buff-colored neck with black head and face | Statement: [nēnē, plumageDescription, buff-colored neck with black head and face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plumageDescription Context triple: [nēnē, plumageDescription, buff-colored neck with black head and face]
-
A.
plumageFeature
chosen
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
B.
malePlumage
Indicates that the specified plumage belongs to or characterizes the male individual of a species.
-
C.
legFeathering
Indicates that an entity possesses feathers growing on or covering its legs.
-
D.
beakType
Indicates the specific form or structure of an entity’s beak, characterizing how it is shaped or adapted.
-
E.
hasBeak
Indicates that an entity possesses a beak as a physical anatomical feature.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b172e88190a26d31c9075b81fb |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.