Triple
T17119350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacques Cartier Bridge |
E415423
|
entity |
| Predicate | hasLightingInstallation |
P1280
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jacques Cartier Bridge, hasLightingInstallation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLightingInstallation Context triple: [Jacques Cartier Bridge, hasLightingInstallation, yes]
-
A.
hasLighting
chosen
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
hasLightingImprovements
Indicates that an entity has enhancements or upgrades made to its lighting conditions or systems.
-
C.
lightingRequirement
Indicates the level or type of light that is needed for something to function, grow, or be used properly.
-
D.
hasLightingEffect
Indicates that one entity applies, produces, or is associated with a particular lighting effect on another entity or environment.
-
E.
lightingControlledBy
Indicates that the lighting system or device is operated, regulated, or influenced by a specified controller or control mechanism.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e8086a388190a655a044feccab14 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.