Triple
T4373318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garter mantle |
E98944
|
entity |
| Predicate | hasEmblemPlacement |
P34701
|
FINISHED |
| Object | left side of the mantle |
—
|
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 side of the mantle | Statement: [Garter mantle, hasEmblemPlacement, left side of the mantle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmblemPlacement Context triple: [Garter mantle, hasEmblemPlacement, left side of the mantle]
-
A.
positionOfEmblem
chosen
Indicates the spatial placement or location of an emblem relative to a reference object or surface.
-
B.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
-
C.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
D.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
E.
addsProtectiveEmblem
Indicates that one entity applies or attaches a protective emblem or symbol to 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521f7d9c81909c9209fe59d20ffd |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.