Triple
T10680010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | buff laced Cochin |
E251720
|
entity |
| Predicate | showQualityTraits |
P5084
|
FINISHED |
| Object | abundant soft feathering |
—
|
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: abundant soft feathering | Statement: [buff laced Cochin, showQualityTraits, abundant soft feathering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showQualityTraits Context triple: [buff laced Cochin, showQualityTraits, abundant soft feathering]
-
A.
storageQuality
Indicates the degree or standard of how well something is stored, such as its preservation, safety, or suitability for use.
-
B.
supportsQuality
Indicates that one entity contributes to maintaining, enhancing, or ensuring the quality or standard of another entity or process.
-
C.
typicalFeatures
chosen
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
D.
hasSurfaceQuality
Indicates that one entity possesses a particular characteristic or condition of its surface.
-
E.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
- 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.