Triple
T14310163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kőbánya-Kispest |
E354805
|
entity |
| Predicate | servesAsTerminusDirection |
P43881
|
FINISHED |
| Object | southeastern terminus of M3 |
—
|
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: southeastern terminus of M3 | Statement: [Kőbánya-Kispest, servesAsTerminusDirection, southeastern terminus of M3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsTerminusDirection Context triple: [Kőbánya-Kispest, servesAsTerminusDirection, southeastern terminus of M3]
-
A.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
B.
direction2Terminus
Indicates the direction in which something leads toward or ends at a particular terminus or endpoint.
-
C.
servedByDirection
Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
-
D.
locatedAtTerminusOf
chosen
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
-
E.
terminusAdjacentTo
Indicates that one terminus (end point) of a route, line, or feature is directly next to or immediately bordering another terminus.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b26da48190a96e2f60ace51335 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.