Triple
T27459976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carway border crossing |
E692707
|
entity |
| Predicate | hasUSPortCode |
P24997
|
FINISHED |
| Object | 3325 |
—
|
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: 3325 | Statement: [Carway border crossing, hasUSPortCode, 3325]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUSPortCode Context triple: [Carway border crossing, hasUSPortCode, 3325]
-
A.
hasUSAN
Indicates that an entity has a specified United States Adopted Name (USAN), typically a nonproprietary name assigned to a pharmaceutical substance.
-
B.
hasPortCode
chosen
Indicates that an entity (such as a port or terminal) is associated with a specific standardized port code identifier.
-
C.
hasUNLocode
Indicates that an entity is associated with a specific UN/LOCODE, identifying its location in the United Nations location code system.
-
D.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
E.
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.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 12:49 p.m.