Triple
T29531171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plymouth Rock chicken |
E749205
|
entity |
| Predicate | featherPatternCommon |
P4572
|
FINISHED |
| Object | barred |
—
|
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: barred | Statement: [Plymouth Rock chicken, featherPatternCommon, barred]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featherPatternCommon Context triple: [Plymouth Rock chicken, featherPatternCommon, barred]
-
A.
wingPattern
Indicates the characteristic arrangement or design present on an entity's wings.
-
B.
featherTypeIndicates
Indicates that a particular type or characteristic of feathers signifies or conveys information about another property, status, or classification of the entity.
-
C.
plumageFeature
chosen
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
D.
furPattern
Indicates the type or arrangement of fur markings or coloration that characterizes an entity’s coat.
-
E.
plumageFunction
Indicates the role or purpose that an organism’s plumage serves, such as in display, camouflage, thermoregulation, or other functions.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cc2656081908adb6f119caa0cc1 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:53 p.m.