Triple
T15658688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobiano Golf Course |
E376513
|
entity |
| Predicate | hasRouting |
P37949
|
FINISHED |
| Object | out-and-back routing |
—
|
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: out-and-back routing | Statement: [Tobiano Golf Course, hasRouting, out-and-back routing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouting Context triple: [Tobiano Golf Course, hasRouting, out-and-back routing]
-
A.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
-
B.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
C.
hasRouteFeature
chosen
Indicates that a route possesses or is associated with a specific characteristic, attribute, or feature.
-
D.
hasNavigationRoute
Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
-
E.
supportsHierarchicalRouting
Indicates that one entity enables or is compatible with routing that uses a multi-level or hierarchical structure of routing domains or paths.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef3cb8c8190a10815b675b341c1 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.