Triple
T35840915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quebec Route 20 |
E1036073
|
entity |
| Predicate | isSecondaryFunction |
P2114
|
FINISHED |
| Object | commuter traffic to and from Montreal |
—
|
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: commuter traffic to and from Montreal | Statement: [Quebec Route 20, isSecondaryFunction, commuter traffic to and from Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSecondaryFunction Context triple: [Quebec Route 20, isSecondaryFunction, commuter traffic to and from Montreal]
-
A.
secondaryFunction
chosen
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
B.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
C.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
D.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
E.
hasSecondarySee
Indicates that an entity has an additional, secondary “see also” reference or cross-link to another related entity.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.