Triple
T3889472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dixie |
E88022
|
entity |
| Predicate | disposability |
P51669
|
FINISHED |
| Object | intended for single use |
—
|
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: intended for single use | Statement: [Dixie, disposability, intended for single use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disposability Context triple: [Dixie, disposability, intended for single use]
-
A.
reusability
Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
-
B.
disappearance
Indicates that an entity ceases to be present, visible, or detectable in a given context or location.
-
C.
disadvantage
Indicates that one entity is in a less favorable, weaker, or hindered position relative to another in a given context.
-
D.
decline
Indicates a decrease or reduction in the level, amount, quality, or intensity of something over time.
-
E.
bodyDisposedIn
Indicates that a body (typically a dead organism or corpse) is placed, discarded, or otherwise disposed of within a particular location or container.
- F. None of above. chosen
Provenance (4 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecaee7148190ada451ccfc6582ee |
completed | March 9, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:21 p.m.