Triple
T19840879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Numedal Line |
E476722
|
entity |
| Predicate | primaryEraOfRegularPassengerService |
P137542
|
FINISHED |
| Object | 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: 20th century | Statement: [Numedal Line, primaryEraOfRegularPassengerService, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEraOfRegularPassengerService Context triple: [Numedal Line, primaryEraOfRegularPassengerService, 20th century]
-
A.
firstPassengerTrainDate
Indicates the calendar date on which the first passenger train service for the subject began operating.
-
B.
historicalTramEra
Indicates that the subject is associated with a specific historical period or era in which tram systems operated or were characteristic.
-
C.
busServiceOpeningDate
Indicates the date on which a particular bus service first began operating.
-
D.
openingDateToRapidTransit
Indicates the date on which a rapid transit service or connection was opened or became operational.
-
E.
primaryEraEvaluated
Indicates that an entity has been assessed or analyzed with respect to its main or most relevant historical era or time period.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6580576748190b85e234b01209ae7 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.