Triple
T32319096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BE-WBR |
E825722
|
entity |
| Predicate | hasThreeLetterSubdivisionSuffix |
P12826
|
FINISHED |
| Object | WBR |
—
|
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: WBR | Statement: [BE-WBR, hasThreeLetterSubdivisionSuffix, WBR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThreeLetterSubdivisionSuffix Context triple: [BE-WBR, hasThreeLetterSubdivisionSuffix, WBR]
-
A.
hasSubdivisionName3
Indicates that an entity has a third-level subdivision whose name is given by the associated value.
-
B.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
-
C.
hasSubdivisionCodePart
Indicates that an entity’s subdivision code includes or is composed of the referenced code segment or component.
-
D.
hasThreeLetterForm
chosen
Indicates that an entity’s written or symbolic form consists of exactly three letters.
-
E.
hasISO3166-2CodePrefix
Indicates that one entity’s ISO 3166-2 code begins with, or is prefixed by, the code of 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 12:46 a.m.