Triple
T35059543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perkinsville, Arizona |
E1011555
|
entity |
| Predicate | railroadFunctionHistorically |
P28401
|
FINISHED |
| Object | water stop |
—
|
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: water stop | Statement: [Perkinsville, Arizona, railroadFunctionHistorically, water stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadFunctionHistorically Context triple: [Perkinsville, Arizona, railroadFunctionHistorically, water stop]
-
A.
hasRailroadHistory
chosen
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
B.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
C.
railroadOrigin
Indicates that a railroad or rail line begins, originates, or has its starting point at a specified location or entity.
-
D.
formerRailroad
Indicates that an entity was previously a railroad but no longer functions as one.
-
E.
usedByRailroad
Indicates that something is utilized or operated by a railroad or railway company.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.