Triple
T11801925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue Saint-Paul |
E280646
|
entity |
| Predicate | isNearbyAttractionOf |
P3449
|
FINISHED |
| Object | Old Quebec historic sites |
—
|
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: Old Quebec historic sites | Statement: [Rue Saint-Paul, isNearbyAttractionOf, Old Quebec historic sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearbyAttractionOf Context triple: [Rue Saint-Paul, isNearbyAttractionOf, Old Quebec historic sites]
-
A.
hasAttractionNearby
chosen
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
B.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
C.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
D.
isPartOfAttraction
Indicates that something is a component or sub-element within a larger attraction or point of interest.
-
E.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.