Triple
T8364591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentish plover |
E197093
|
entity |
| Predicate | maleBreedingPlumageFeature |
P82321
|
FINISHED |
| Object | black ear-covert patch |
—
|
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: black ear-covert patch | Statement: [Kentish plover, maleBreedingPlumageFeature, black ear-covert patch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maleBreedingPlumageFeature Context triple: [Kentish plover, maleBreedingPlumageFeature, black ear-covert patch]
-
A.
malePlumage
Indicates that the specified plumage belongs to or characterizes the male individual of a species.
-
B.
femalePlumageFeature
Indicates that the specified plumage feature is characteristic of the female individual in a species.
-
C.
plumageFeature
Indicates a relationship where a specific characteristic or attribute is associated with an entity’s plumage (feathers).
-
D.
nonBreedingPlumageColor
Indicates the coloration an organism displays in its non-breeding (non-reproductive) plumage phase.
-
E.
plumageColorCommon
Indicates that two entities share the same typical or most frequently observed plumage color.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808a67f88190849152102bfeb574 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6 p.m.