Triple
T27719753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turlock Transit |
E698918
|
entity |
| Predicate | transportationSystemFor |
P941
|
FINISHED |
| Object | city of Turlock |
—
|
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: city of Turlock | Statement: [Turlock Transit, transportationSystemFor, city of Turlock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationSystemFor Context triple: [Turlock Transit, transportationSystemFor, city of Turlock]
-
A.
hasTransportationSystem
chosen
Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
-
B.
rapidTransitSystem
Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
-
C.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
D.
typeOfTransportInfrastructure
Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
-
E.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 3:06 p.m.