Triple
T25137189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pease International Tradeport |
E629690
|
entity |
| Predicate | openedAsTradeport |
P67026
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Pease International Tradeport, openedAsTradeport, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsTradeport Context triple: [Pease International Tradeport, openedAsTradeport, 1990s]
-
A.
openedPortToForeignTrade
Indicates that an entity has allowed or enabled a port to conduct commercial trade with foreign countries.
-
B.
openedForTrade
chosen
Indicates that an entity has begun allowing commercial transactions or trading activities to occur.
-
C.
openedPort
Indicates that a network port on a host or device is currently open and able to accept incoming connections.
-
D.
openedAsTerminus
Indicates that a transportation line or route was initially opened with this location serving as its end-point terminus.
-
E.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 6:29 a.m.