Triple
T28626678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Lakes industrial corridor |
E724543
|
entity |
| Predicate | includesPortCity |
P2745
|
FINISHED |
| Object | Chicago |
—
|
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: Chicago | Statement: [Great Lakes industrial corridor, includesPortCity, Chicago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPortCity Context triple: [Great Lakes industrial corridor, includesPortCity, Chicago]
-
A.
hasPortCity
chosen
Indicates that a place or region possesses or is associated with a city that functions as its port.
-
B.
isPortCityOn
Indicates that a city functions as a port located on the specified body of water.
-
C.
includesPort
Indicates that one entity contains, encompasses, or has as part of it a specific port or set of ports.
-
D.
hasPortCityCharacteristicsOf
Indicates that one entity possesses or exhibits the defining features, functions, or qualities typically associated with a port city of another entity.
-
E.
portCityInvolved
Indicates that a port city participates in, is affected by, or plays a role in a specified event, process, or relationship.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: April 28, 2026, 4:36 a.m.