Triple
T33626272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budapest transport network |
E861412
|
entity |
| Predicate | hasRiverLine |
P36817
|
FINISHED |
| Object | Boat line D11 |
—
|
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: Boat line D11 | Statement: [Budapest transport network, hasRiverLine, Boat line D11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverLine Context triple: [Budapest transport network, hasRiverLine, Boat line D11]
-
A.
hasRiverCode
Indicates that a river is associated with a specific identifying code or classification value.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
D.
hasBoatLine
chosen
Indicates that one entity operates, owns, or is associated with a particular boat service or boat route line.
-
E.
hasCityOnRiver
Indicates that a city is located on or along the course of a particular river.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1:41 a.m.