Triple
T18342766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Lewiston |
E439450
|
entity |
| Predicate | openedForCommercialNavigation |
P131442
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Port of Lewiston, openedForCommercialNavigation, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForCommercialNavigation Context triple: [Port of Lewiston, openedForCommercialNavigation, 1975]
-
A.
openedForCommercialService
Indicates that something (such as a facility, route, or service) began operating and became available for regular commercial use.
-
B.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
-
C.
openedForUseAs
Indicates that something was made available and began functioning in the capacity or role specified by another entity or purpose.
-
D.
openedForUseBy
Indicates that something has been made available or activated so that a particular entity can use it.
-
E.
openedForCurrentUse
Indicates that an entity has been opened and is currently available for its intended use or operation.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f188e081909cdbce61a21b9591 |
completed | April 19, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e4561d665081908ec555344e76d82b |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 10:37 a.m.