Triple
T24773025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:GB |
E619780
|
entity |
| Predicate | usesParentCode |
P85321
|
FINISHED |
| Object | GB |
—
|
NE NERFINISHED |
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: GB | Statement: [ISO 3166-2:GB, usesParentCode, GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesParentCode Context triple: [ISO 3166-2:GB, usesParentCode, GB]
-
A.
hasParentCode
chosen
Indicates that an entity is associated with a parent code from which it is derived or to which it is hierarchically linked.
-
B.
usedAsParentFor
Indicates that one entity functions as the parent or container for another entity within a hierarchical or structural relationship.
-
C.
usedByParentCompany
Indicates that something (such as a resource, product, or service) is utilized or employed by a parent company in relation to its operations or activities.
-
D.
sometimesConsideredParent
Indicates that an entity is on occasion regarded or treated as a parent of another entity, but this parental relationship is not consistently or universally recognized.
-
E.
hasParentProgram
Indicates that a given program is hierarchically contained within or derived from another, higher-level program that serves as its parent.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410acff0481908b72047fe19d97de |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:32 a.m.