Triple
T796393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nēnē |
E17031
|
entity |
| Predicate | neckPattern |
P8034
|
FINISHED |
| Object | distinctive furrowed or barred neck feathers |
—
|
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: distinctive furrowed or barred neck feathers | Statement: [nēnē, neckPattern, distinctive furrowed or barred neck feathers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neckPattern Context triple: [nēnē, neckPattern, distinctive furrowed or barred neck feathers]
-
A.
hatPattern
Indicates that one entity has a hat characterized by a specific pattern or design.
-
B.
kitPattern
Indicates the design or visual pattern featured on a team's kit or uniform.
-
C.
notationPattern
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
D.
pattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
E.
crestColor
Indicates the color characteristic of an entity’s crest.
- 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.