Triple
T17621912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corriedale sheep |
E429727
|
entity |
| Predicate | woolQuality |
P35372
|
FINISHED |
| Object | good spinning quality |
—
|
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: good spinning quality | Statement: [Corriedale sheep, woolQuality, good spinning quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: woolQuality Context triple: [Corriedale sheep, woolQuality, good spinning quality]
-
A.
hasGrainQuality
Indicates that an entity possesses a particular level or type of grain quality, characterizing the quality attributes of its grain.
-
B.
fiberCharacteristic
chosen
Indicates a relationship where a specific characteristic or property is attributed to a fiber or fibrous material.
-
C.
textileType
Indicates the specific kind or category of textile material associated with an entity.
-
D.
colorGrade
Indicates the qualitative or categorical assessment of an entity’s color according to a defined grading scale.
-
E.
fiberwiseDescription
Indicates a description or characterization that is given separately for each fiber in a fibered or parameterized structure, specifying how the relationship or action behaves over individual fibers.
- 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.