Triple
T10753578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorel-Tracy |
E253631
|
entity |
| Predicate | hasIndustrialPort |
P95801
|
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: [Sorel-Tracy, hasIndustrialPort, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustrialPort Context triple: [Sorel-Tracy, hasIndustrialPort, yes]
-
A.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
B.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
C.
hasIndustrialTown
Indicates that an entity possesses or is associated with a town characterized primarily by industrial activities or facilities.
-
D.
isInlandPort
Indicates that a port facility is located inland, away from the open sea, typically on a river, canal, or lake, while still serving maritime or shipping functions.
-
E.
isAmongLargestPortsIn
Indicates that a port ranks among the largest ports within a specified geographic or administrative area.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71dc2543c8190bb060aa7a1fed6a6 |
completed | April 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:15 p.m.