Triple
T1735062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikidata |
E37902
|
entity |
| Predicate | SPARQLEndpointURL |
P6055
|
FINISHED |
| Object | https://query.wikidata.org/sparql |
—
|
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://query.wikidata.org/sparql | Statement: [Wikidata, SPARQLEndpointURL, https://query.wikidata.org/sparql]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SPARQLEndpointURL Context triple: [Wikidata, SPARQLEndpointURL, https://query.wikidata.org/sparql]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
C.
endPointExample
Indicates that something serves as a representative or illustrative instance of a particular endpoint.
-
D.
EUAccession
Indicates that an entity becomes a member state of the European Union through the formal accession process.
-
E.
hasEndpointCity
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.