Triple
T18052528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceiba |
E431954
|
entity |
| Predicate | fiberUsedFor |
P1272
|
FINISHED |
| Object | stuffing pillows |
—
|
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: stuffing pillows | Statement: [Ceiba, fiberUsedFor, stuffing pillows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiberUsedFor Context triple: [Ceiba, fiberUsedFor, stuffing pillows]
-
A.
fiberContent
Indicates that one entity specifies the amount or presence of dietary fiber contained in another entity.
-
B.
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.
-
C.
fiberType
Indicates the specific kind or classification of fiber that characterizes or composes an entity.
-
D.
fiberCharacteristic
Indicates a relationship where a specific characteristic or property is attributed to a fiber or fibrous material.
-
E.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c0ff580c8190bc3ca04025476255 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.