Triple
T26493899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Order 191 |
E669227
|
entity |
| Predicate | foundWrappedWith |
P104424
|
FINISHED |
| Object | cigars |
—
|
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: cigars | Statement: [Special Order 191, foundWrappedWith, cigars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundWrappedWith Context triple: [Special Order 191, foundWrappedWith, cigars]
-
A.
isTraditionallyWrappedWhen
Indicates that something is customarily enclosed or covered in another material or item during a particular time, event, or circumstance.
-
B.
canBeWrappedBy
Indicates that one entity is capable of being enclosed, covered, or surrounded by another entity.
-
C.
foundWith
chosen
Indicates that one entity is discovered, observed, or obtained in the presence or company of another entity.
-
D.
canWrap
Indicates that one entity is able to enclose, cover, or surround another entity, typically forming an outer layer or container around it.
-
E.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 1:06 a.m.