Triple
T30847534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Vertiz |
E785679
|
entity |
| Predicate | hasRoadTransportConnection |
P3791
|
FINISHED |
| Object | local bus routes |
—
|
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: local bus routes | Statement: [Dr. Vertiz, hasRoadTransportConnection, local bus routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadTransportConnection Context triple: [Dr. Vertiz, hasRoadTransportConnection, local bus routes]
-
A.
hasBridgeOrFerryConnection
Indicates that there exists a bridge or ferry link enabling direct passage or transport between the related entities.
-
B.
hasPublicTransportConnection
chosen
Indicates that there is an available public transportation link or service connecting the related entities.
-
C.
hasRoadConnectionRegion
Indicates that there is a road-based transportation link connecting one region to another.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
hasGoodTransportLinks
Indicates that a place is well connected to other locations by efficient and convenient transport options.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 29, 2026, 8:46 p.m.