Triple
T11067253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flame of Liberty |
E261656
|
entity |
| Predicate | nearEventSite |
P66088
|
FINISHED |
| Object | Pont de l'Alma tunnel car crash of 31 August 1997 |
—
|
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: Pont de l'Alma tunnel car crash of 31 August 1997 | Statement: [Flame of Liberty, nearEventSite, Pont de l'Alma tunnel car crash of 31 August 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearEventSite Context triple: [Flame of Liberty, nearEventSite, Pont de l'Alma tunnel car crash of 31 August 1997]
-
A.
nearbyEvent
chosen
Indicates that one event occurs close in space or time to another event.
-
B.
nearPass
Indicates that one entity moves or travels close to another entity without necessarily making direct contact or interaction.
-
C.
notableNearbySite
Indicates that one entity is a significant or noteworthy site located close to another entity.
-
D.
meetsNear
Indicates that two entities meet or come together at a location that is in close proximity to a specified reference point or area.
-
E.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79920428c81908db824ab54e08e8d |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.