Triple
T26581840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 500 |
E667099
|
entity |
| Predicate | formsMainSectionOf |
P112183
|
FINISHED |
| Object | Trans-Labrador Highway east–west corridor |
—
|
NE NERFINISHED |
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: Trans-Labrador Highway east–west corridor | Statement: [Route 500, formsMainSectionOf, Trans-Labrador Highway east–west corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsMainSectionOf Context triple: [Route 500, formsMainSectionOf, Trans-Labrador Highway east–west corridor]
-
A.
formsFacadeOf
Indicates that one entity serves as the outward-facing surface or front (facade) of another entity, typically concealing or enclosing it.
-
B.
formsFocalPointOf
Indicates that something serves as the central or primary point of attention, interest, or activity within a given context or arrangement.
-
C.
formsMostOf
Indicates that one entity constitutes the majority or predominant portion of another entity.
-
D.
formsTopOf
Indicates that one entity constitutes the uppermost part or surface of another entity.
-
E.
primarySection
chosen
Indicates that one entity is the main or most important section or subdivision associated with another 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 2:03 a.m.