Triple
T19040989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Alaska Pipeline System |
E465999
|
entity |
| Predicate | endFeature |
P48547
|
FINISHED |
| Object | ice-free port of Valdez |
—
|
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: ice-free port of Valdez | Statement: [Trans-Alaska Pipeline System, endFeature, ice-free port of Valdez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endFeature Context triple: [Trans-Alaska Pipeline System, endFeature, ice-free port of Valdez]
-
A.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
B.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
C.
endTheme
Indicates that something serves as the concluding or final thematic element within a larger sequence, work, or context.
-
D.
endName
Indicates that one entity serves as the ending or final name/designation associated with another entity.
-
E.
endOrTransformation
Indicates a point at which something either concludes or changes into a different state or form.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80054c88190a9d3a49aed504235 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.