Triple
T34933589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Monument (Christopher Wren column) |
E1007506
|
entity |
| Predicate | hasFlameUrn |
P182454
|
FINISHED |
| Object | gilded urn of fire at the top |
—
|
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: gilded urn of fire at the top | Statement: [The Monument (Christopher Wren column), hasFlameUrn, gilded urn of fire at the top]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlameUrn Context triple: [The Monument (Christopher Wren column), hasFlameUrn, gilded urn of fire at the top]
-
A.
hasEternalFlame
Indicates that an entity possesses or maintains a flame that is intended to burn perpetually without being extinguished.
-
B.
hasMemorialFlame
Indicates that a memorial or commemorative site includes or is associated with an eternal or symbolic flame.
-
C.
canFullyEncaseBodyInFlames
Indicates that an entity has the ability to completely surround and cover its entire body with flames.
-
D.
lightingOfEternalFlameInitiatedBy
Indicates that the action of lighting an eternal flame is initiated or carried out by a specified agent or entity.
-
E.
hasCrematorium
Indicates that one entity possesses, contains, or is equipped with a crematorium facility.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 3, 2026, 4 p.m.