Triple
T5014811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British National Grid |
E112713
|
entity |
| Predicate | typicalPrecision |
P57967
|
FINISHED |
| Object | 1 metre or better |
—
|
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: 1 metre or better | Statement: [British National Grid, typicalPrecision, 1 metre or better]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPrecision Context triple: [British National Grid, typicalPrecision, 1 metre or better]
-
A.
typicalConsistency
Indicates that one entity characteristically maintains a regular or expected level of consistency in relation to another entity or context.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
accuracyCivilianTypical
Indicates the degree to which something typically achieves accurate results or effects when applied to civilians.
-
D.
typicalMeasure
chosen
Indicates the standard or characteristic quantitative measure typically associated with something, such as its usual size, weight, duration, or other magnitude.
-
E.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732e0b848190858407920e7aefd0 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.