Triple
T14998108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cass Scenic Railroad State Park |
E374011
|
entity |
| Predicate | eraOfLoggingOperations |
P97447
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Cass Scenic Railroad State Park, eraOfLoggingOperations, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfLoggingOperations Context triple: [Cass Scenic Railroad State Park, eraOfLoggingOperations, early 20th century]
-
A.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
-
B.
eraOfMajorOperation
chosen
Indicates the historical period during which a major operation primarily took place or was most active.
-
C.
loggingMode
Indicates the configuration or method by which events, actions, or data are recorded in logs.
-
D.
loggingTool
Indicates that an entity serves as or uses a tool specifically intended for logging events, data, or activities.
-
E.
operationalHistory
Indicates the record of how something has been used, functioned, or operated over time, including its past activities and events.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded71a5618819083ae96a79735ef98 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.