Triple
T18526265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BD |
E452724
|
entity |
| Predicate | associatedRailwayLine |
P848
|
FINISHED |
| Object | Java main line |
—
|
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: Java main line | Statement: [BD, associatedRailwayLine, Java main line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRailwayLine Context triple: [BD, associatedRailwayLine, Java main line]
-
A.
railwayLine
chosen
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
ownsRailwayLine
Indicates that one entity has legal ownership or control over a railway line used for train operations.
-
C.
relatedRailroad
Indicates that there is an association or connection between an entity and a specific railroad, such as ownership, operation, service, or historical linkage.
-
D.
formerRailwayLine
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
-
E.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53392618c8190b44de46b80ee6a6d |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.