Triple
T17702685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polytechnique |
E441346
|
entity |
| Predicate | filmLocationTime |
P128658
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Polytechnique, filmLocationTime, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmLocationTime Context triple: [Polytechnique, filmLocationTime, 1989]
-
A.
filmLocationFor
Indicates a relationship where a specific place serves as the filming location for a particular film or production.
-
B.
filmingLocationContext
Indicates the contextual relationship specifying where the filming of an event, scene, or production took place.
-
C.
plotLocation
Indicates the relationship between a creative work and the place or setting where its story or events occur.
-
D.
formerFilmingLocation
Indicates that a place was once used as a filming location for a work but is no longer used for that purpose.
-
E.
locatedAtTime
Indicates that a location relationship holds during a specific time or time interval.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729528b88190bd8a104f6f6d4e69 |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d018227c8190b6624a2199e765e8 |
completed | April 18, 2026, 6:40 p.m. |
Created at: April 10, 2026, 10:05 a.m.