Triple
T27029207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agglomération de Longueuil |
E680871
|
entity |
| Predicate | sharesServicesFor |
P75411
|
FINISHED |
| Object | public transit |
—
|
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: public transit | Statement: [Agglomération de Longueuil, sharesServicesFor, public transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesServicesFor Context triple: [Agglomération de Longueuil, sharesServicesFor, public transit]
-
A.
sharesServicesWith
chosen
Indicates that two entities make use of, provide, or are connected through the same services or service infrastructure.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesResourcesWith
Indicates that two entities mutually use, access, or allocate the same resources.
-
D.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
E.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 27, 2026, 7:12 a.m.