Triple
T8534824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Halles |
E202051
|
entity |
| Predicate | demolishedMarketHalls |
P29327
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Les Halles, demolishedMarketHalls, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolishedMarketHalls Context triple: [Les Halles, demolishedMarketHalls, 1970s]
-
A.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
B.
demolishedOriginalStructures
chosen
Indicates that one entity has completely destroyed or removed the original structures associated with another entity.
-
C.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
-
D.
traditionallyDestroyedAt
Indicates that something is customarily or historically destroyed at a particular time, place, or event according to tradition.
-
E.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a0ccd4819097b41d0dfb1c5018 |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:17 p.m.