Triple
T10679737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mottled Cochin |
E251711
|
entity |
| Predicate | isSelectedFor |
P10044
|
FINISHED |
| Object | plumage pattern |
—
|
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: plumage pattern | Statement: [mottled Cochin, isSelectedFor, plumage pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSelectedFor Context triple: [mottled Cochin, isSelectedFor, plumage pattern]
-
A.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
B.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
C.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
D.
selectedTo
chosen
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
E.
usedToSelect
Indicates that one entity serves as a criterion, tool, or basis for choosing or determining another entity.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc03dc4819080a6211a2bfaaf0a |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.