Triple
T33496951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tram line 4 (Budapest) |
E857886
|
entity |
| Predicate | connectsToMetroLineAt |
P199130
|
FINISHED |
| Object | M3 at Nyugati tér |
—
|
NE NERFINISHED |
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: M3 at Nyugati tér | Statement: [Tram line 4 (Budapest), connectsToMetroLineAt, M3 at Nyugati tér]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToMetroLineAt Context triple: [Tram line 4 (Budapest), connectsToMetroLineAt, M3 at Nyugati tér]
-
A.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
B.
metroLineCode
Indicates the specific code or identifier assigned to a metro (subway) line with which an entity is associated.
-
C.
servedByTramwayLine
Indicates that a location or area is provided public transport service by a specific tramway line.
-
D.
metroLineInaugurated
Indicates that a metro line was officially opened and began operation on a specific date or during a specific event.
-
E.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
| PDg | Predicate description generation | batch_69ff21ca6964819088bdf1810b7863f2 |
completed | May 9, 2026, noon |
Created at: May 1, 2026, 1:38 a.m.