Triple
T18998838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LIPZ |
E464890
|
entity |
| Predicate | isServedByTransport |
P133438
|
FINISHED |
| Object | bus |
—
|
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: bus | Statement: [LIPZ, isServedByTransport, bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isServedByTransport Context triple: [LIPZ, isServedByTransport, bus]
-
A.
servedByTransportation
chosen
Indicates that a location or entity is provided access or connection by a particular mode or service of transportation.
-
B.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
C.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
-
D.
hasPublicTransitRole
Indicates that an entity holds a specific functional role or responsibility within a public transit system.
-
E.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6838f4481909b265e29964b0dca |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.