Triple
T3427141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directions API |
E72251
|
entity |
| Predicate | endpointBaseURL |
P6055
|
FINISHED |
| Object | https://maps.googleapis.com/maps/api/directions |
—
|
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: https://maps.googleapis.com/maps/api/directions | Statement: [Directions API, endpointBaseURL, https://maps.googleapis.com/maps/api/directions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointBaseURL Context triple: [Directions API, endpointBaseURL, https://maps.googleapis.com/maps/api/directions]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
endPointExample
Indicates that something serves as a representative or illustrative instance of a particular endpoint.
-
C.
hasEndpointCity
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
-
D.
endpointRegion
Indicates that one entity serves as the geographic or logical region in which the other entity’s endpoint is located or configured.
-
E.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb982792c8190b1163eee4252210f |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.