Triple
T25791544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Place Monument |
E649559
|
entity |
| Predicate | removalOrderedBy |
P23790
|
FINISHED |
| Object | Mayor Mitch Landrieu |
—
|
NE NERFINISHED |
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: Mayor Mitch Landrieu | Statement: [Liberty Place Monument, removalOrderedBy, Mayor Mitch Landrieu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removalOrderedBy Context triple: [Liberty Place Monument, removalOrderedBy, Mayor Mitch Landrieu]
-
A.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
B.
demolitionOrderedBy
chosen
Indicates that an authority or agent has formally issued an order for the demolition of a specified object or structure.
-
C.
originallyOrderedBy
Indicates that one entity was the initial source or originator of an order or request for another entity.
-
D.
orderedProtectionBy
Indicates that one entity has formally requested or arranged protective measures to be provided by another entity.
-
E.
movementOrderedBy
Indicates that one entity’s movement occurs according to, or is arranged/controlled by, another entity’s ordering or directive.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5feff92388190824ab9cccb0224ef |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 6 a.m.