Triple
T26362873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Trois-Rivières |
E660254
|
entity |
| Predicate | portAuthorityType |
P160454
|
FINISHED |
| Object | Canadian Port Authority |
—
|
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: Canadian Port Authority | Statement: [Port of Trois-Rivières, portAuthorityType, Canadian Port Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portAuthorityType Context triple: [Port of Trois-Rivières, portAuthorityType, Canadian Port Authority]
-
A.
transportAuthorityType
Indicates the specific kind or category of authority responsible for overseeing or regulating transportation.
-
B.
passengerTerminalType
Indicates the specific kind or category of passenger terminal associated with an entity.
-
C.
airportTypeManaged
Indicates that an entity is responsible for managing or overseeing a particular type or category of airport.
-
D.
typeOfPortFacility
Indicates that one port facility is classified as a specific type or category of port facility in relation to another.
-
E.
airportAccessMode
Indicates the typical mode or method of transportation used to access or reach an airport.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f610293cd88190894969a031f85edd |
completed | May 2, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 10:53 p.m.