Triple
T1161702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palais des Arts Libéraux |
E24505
|
entity |
| Predicate | temporalStatus |
P127
|
FINISHED |
| Object | demolished |
—
|
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: demolished | Statement: [Palais des Arts Libéraux, temporalStatus, demolished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalStatus Context triple: [Palais des Arts Libéraux, temporalStatus, demolished]
-
A.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
-
B.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
C.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
-
D.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
historicalRecordStatus
Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb1915081908834ced85d09e299 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.