Triple
T3225519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Mason |
E67610
|
entity |
| Predicate | monumentStatus |
P46320
|
FINISHED |
| Object | statue relocated due to controversy |
—
|
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: statue relocated due to controversy | Statement: [John Mason, monumentStatus, statue relocated due to controversy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monumentStatus Context triple: [John Mason, monumentStatus, statue relocated due to controversy]
-
A.
monumentState
Indicates that a monument is located within, or officially associated with, a particular state or state-level administrative region.
-
B.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
C.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
D.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
E.
governingBodyForLandmarkStatus
Indicates the organization or authority that holds official responsibility for designating and overseeing a landmark’s protected or special status.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adae1c51a48190b4a395650528b5d8 |
completed | March 8, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada149df58819091173b14b49582b1 |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:08 p.m.