Triple
T6251737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red-necked phalarope |
E140059
|
entity |
| Predicate | nonBreedingPlumageFeature |
P4572
|
FINISHED |
| Object | mostly grey and white |
—
|
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: mostly grey and white | Statement: [red-necked phalarope, nonBreedingPlumageFeature, mostly grey and white]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonBreedingPlumageFeature Context triple: [red-necked phalarope, nonBreedingPlumageFeature, mostly grey and white]
-
A.
plumageFeature
chosen
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
B.
plumageColorCommon
Indicates that two entities share the same typical or most frequently observed plumage color.
-
C.
plumageColorSource
Indicates the relationship by which the color of an entity’s plumage is derived from or attributed to a particular source.
-
D.
malePlumage
Indicates that the specified plumage belongs to or characterizes the male individual of a species.
-
E.
underpartsColor
Indicates the color characteristic of the lower surface or underside of an entity’s body.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633fb2ac8190b71b8e35fa923300 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.