Triple
T18322518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sainte-Julie |
E438917
|
entity |
| Predicate | hasLocalBusService |
P39381
|
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: [Sainte-Julie, hasLocalBusService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalBusService Context triple: [Sainte-Julie, hasLocalBusService, yes]
-
A.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
B.
hasPublicTransitServiceLevel
Indicates the level or quality of public transit service provided to or available at a given location or entity.
-
C.
hasPublicTransitProvider
Indicates that a place or region is served by a specific public transit operating organization or agency.
-
D.
hasPublicTransitFunction
Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
-
E.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa7be288190983f13e9c7061b6d |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.