Triple
T24745205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NP |
E618676
|
entity |
| Predicate | railroadScope |
P5684
|
FINISHED |
| Object | transcontinental railroad |
—
|
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: transcontinental railroad | Statement: [NP, railroadScope, transcontinental railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadScope Context triple: [NP, railroadScope, transcontinental railroad]
-
A.
railroadServiceScope
chosen
Indicates the extent or coverage area within which a railroad service operates or is applicable.
-
B.
railroad
Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
-
C.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
-
D.
relatedRailroad
Indicates that there is an association or connection between an entity and a specific railroad, such as ownership, operation, service, or historical linkage.
-
E.
railwayFocus
Indicates that something is a primary subject, theme, or point of attention specifically in the context of railways or railway-related matters.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:21 a.m.