Triple
T35219279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B2011 road |
E1016904
|
entity |
| Predicate | hasCountryCodeSystem |
P119761
|
FINISHED |
| Object | Great Britain B-road numbering scheme |
—
|
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: Great Britain B-road numbering scheme | Statement: [B2011 road, hasCountryCodeSystem, Great Britain B-road numbering scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryCodeSystem Context triple: [B2011 road, hasCountryCodeSystem, Great Britain B-road numbering scheme]
-
A.
associatedCountryCodeSystem
chosen
Indicates that there is a relationship between an entity and the country code system it is associated with or governed by.
-
B.
hasPrimaryCountryCode
Indicates that an entity is associated with its main or officially designated country code.
-
C.
isCountryCode
Indicates that one entity is a valid country code designating the country represented by the other entity.
-
D.
telephoneSystemCountry
Indicates that a telephone system operates within, or is associated with, a specific country.
-
E.
UICCountryCode
Indicates that an entity is associated with a specific country identified by its UIC (International Union of Railways) country code.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.