Triple
T10440109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb Guard Identification Badge |
E246144
|
entity |
| Predicate | wearLocationOnUniform |
P18894
|
FINISHED |
| Object | left breast pocket |
—
|
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: left breast pocket | Statement: [Tomb Guard Identification Badge, wearLocationOnUniform, left breast pocket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearLocationOnUniform Context triple: [Tomb Guard Identification Badge, wearLocationOnUniform, left breast pocket]
-
A.
wearsOnUniform
Indicates that an item is part of and is worn as a component of a uniform.
-
B.
wearsUniformSimilarTo
Indicates that one entity wears a uniform that is similar in appearance or style to the uniform worn by another entity.
-
C.
wearsUniformColor
Indicates that an entity regularly uses or is associated with a specific uniform color as part of its standard attire or dress code.
-
D.
wearLocation
chosen
Indicates the typical body part or location on which an item is worn.
-
E.
wornAt
Indicates that an item is being worn on a specific part of the body or at a particular time or event.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:15 p.m.