Triple
T15980455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longueuil–Université-de-Sherbrooke |
E387556
|
entity |
| Predicate | hasIndoorConcourse |
P121149
|
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: [Longueuil–Université-de-Sherbrooke, hasIndoorConcourse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndoorConcourse Context triple: [Longueuil–Université-de-Sherbrooke, hasIndoorConcourse, yes]
-
A.
hasDomesticConcourse
Indicates that a transportation facility includes a concourse area designated for domestic (within-country) passengers or services.
-
B.
isMainConcourseOf
Indicates that one concourse serves as the primary or central concourse within a larger facility or complex.
-
C.
hasOverheadConcourse
Indicates that one location or structure is connected to or served by a concourse that is elevated above ground level or above the main area it serves.
-
D.
hasInternationalConcourse
Indicates that a facility or location includes a concourse designated for international passengers or services.
-
E.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:54 a.m.