Triple
T38243701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Théâtre de Québec |
E1013835
|
entity |
| Predicate | indoorFeature |
P150259
|
FINISHED |
| Object | foyer |
—
|
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: foyer | Statement: [Grand Théâtre de Québec, indoorFeature, foyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorFeature Context triple: [Grand Théâtre de Québec, indoorFeature, foyer]
-
A.
indoorComponent
chosen
Indicates that one entity functions as an indoor part, element, or feature of another entity.
-
B.
homeFacilityIndoor
Indicates that the primary or designated facility associated with an entity is located indoors rather than outdoors.
-
C.
indoorAdvantage
Indicates that an entity has a beneficial edge or improved performance when conditions or activities occur indoors rather than outdoors.
-
D.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
E.
indoorSectionName
Indicates the specific named section or area within an indoor space to which an entity is related.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.