Triple
T17621941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corriedale sheep |
E429727
|
entity |
| Predicate | coatCoverage |
P87207
|
FINISHED |
| Object | well-covered body with wool |
—
|
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: well-covered body with wool | Statement: [Corriedale sheep, coatCoverage, well-covered body with wool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coatCoverage Context triple: [Corriedale sheep, coatCoverage, well-covered body with wool]
-
A.
bandCoverage
Indicates the range or extent of frequencies, wavelengths, or channels that a particular band encompasses or provides.
-
B.
bodyCoverage
chosen
Indicates the extent or proportion of an entity’s body that is covered by another substance, material, or feature.
-
C.
surfaceCover
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
-
D.
bodyCovering
Indicates the type of external covering or surface (such as skin, fur, feathers, or scales) that characterizes an entity’s body.
-
E.
mayCover
Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46db98c54819088dadec9f6bcc559 |
completed | April 19, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.