Triple
T299280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | chicken |
E6161
|
entity |
| Predicate | hasDominanceSystem |
P10563
|
FINISHED |
| Object | pecking order |
—
|
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: pecking order | Statement: [chicken, hasDominanceSystem, pecking order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominanceSystem Context triple: [chicken, hasDominanceSystem, pecking order]
-
A.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
B.
dominantGeneration
Indicates that one generation in a life cycle is more prominent, long-lived, or visually conspicuous than the other generation(s).
-
C.
dominantRegion
Indicates that one region exerts primary control, influence, or prominence over another region within a given context.
-
D.
dominantParty
Indicates that one party in a relationship holds primary control, authority, or influence over the other.
-
E.
hasCorrelativesSystem
Indicates that one entity possesses or employs a system of correlatives—structured, corresponding elements or forms that are systematically related to each other.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9398df08190af40063a2de7a1d0 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea07e3bc8190bae593b3264de211 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.