Triple
T31055977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploshcha Jakuba Kolasa |
E791397
|
entity |
| Predicate | hasCityTransportConnection |
P3791
|
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: [Ploshcha Jakuba Kolasa, hasCityTransportConnection, bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityTransportConnection Context triple: [Ploshcha Jakuba Kolasa, hasCityTransportConnection, bus]
-
A.
hasPublicTransportConnection
chosen
Indicates that there is an available public transportation link or service connecting the related entities.
-
B.
hasGoodPublicTransportConnections
Indicates that an entity is well served by public transportation options, providing convenient and efficient connections to other locations.
-
C.
hasGoodTransportLinks
Indicates that a place is well connected to other locations by efficient and convenient transport options.
-
D.
hasPublicTransitFunction
Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
-
E.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 9 p.m.