Triple
T26520160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copper River and Northwestern Railway |
E669927
|
entity |
| Predicate | builtThrough |
P160600
|
FINISHED |
| Object | glacial terrain |
—
|
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: glacial terrain | Statement: [Copper River and Northwestern Railway, builtThrough, glacial terrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtThrough Context triple: [Copper River and Northwestern Railway, builtThrough, glacial terrain]
-
A.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
B.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
C.
wasBuilt
Indicates that one entity constructed, created, or assembled another entity, typically at a specific time or over a period.
-
D.
builtWithAssistanceFrom
Indicates that something was constructed, created, or developed with help, support, or collaboration from another party.
-
E.
builtInThe
Indicates that something was constructed or created within a specified location, structure, or context.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613c16fbc8190bacc903085dd0e03 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:27 a.m.