Triple
T7616046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jägerndorf |
E172362
|
entity |
| Predicate | railwayJunctionSince |
P78132
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Jägerndorf, railwayJunctionSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayJunctionSince Context triple: [Jägerndorf, railwayJunctionSince, 19th century]
-
A.
railwayJunctionFor
Indicates that a location serves as a junction point where multiple railway lines or routes connect or intersect for a given railway network or service.
-
B.
railwaySectionOpeningDate
Indicates the date on which a specific section of a railway line was officially opened for operation.
-
C.
railInterface
Indicates a connection or interaction between entities via a rail-based system or interface.
-
D.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
-
E.
railwayOpenedWith
Indicates that a railway line or section was inaugurated and began operation together with a specified associated element (such as a station, segment, or service).
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6fe7323b0819081664662d2f26937 |
completed | March 27, 2026, 10:02 p.m. |
Created at: March 27, 2026, 3:55 p.m.