Triple
T26738403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go the Distance |
E674177
|
entity |
| Predicate | BoltonVersionLanguage |
P148411
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Go the Distance, BoltonVersionLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BoltonVersionLanguage Context triple: [Go the Distance, BoltonVersionLanguage, English]
-
A.
officialLanguageVersion
Indicates that one language variant is the officially recognized form or version used for formal or administrative purposes in relation to another language or context.
-
B.
primaryLanguageVersion
chosen
Indicates that one language version of a resource is designated as the main or default version among its language variants.
-
C.
brandLanguageVariant
Indicates that one language variant of a brand is related to or derived from another language version of the same brand.
-
D.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
E.
liturgicalLanguageVersion
Indicates that one entity is a specific version or form of another entity expressed in a particular liturgical language.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:48 a.m.