Triple
T34012944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walk London network |
E872161
|
entity |
| Predicate | hasInformation |
P17720
|
FINISHED |
| Object | downloadable route guides |
—
|
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: downloadable route guides | Statement: [Walk London network, hasInformation, downloadable route guides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInformation Context triple: [Walk London network, hasInformation, downloadable route guides]
-
A.
hasInformationService
Indicates that one entity provides, operates, or is associated with an information-related service for another entity.
-
B.
providedInformationAbout
Indicates that one entity supplied or communicated information or details about another entity or topic to someone.
-
C.
providesInformationIn
chosen
Indicates that one entity supplies or conveys information within or through another entity or context.
-
D.
usesInformationFor
Indicates that one entity applies or exploits information obtained from another entity for a particular purpose or activity.
-
E.
providedInformationOn
Indicates that one entity supplied or communicated specific information or details to another entity.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: May 1, 2026, 1:51 a.m.