Triple
T27669778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J1 |
E697627
|
entity |
| Predicate | countryHighestDivision |
P70432
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [J1, countryHighestDivision, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryHighestDivision Context triple: [J1, countryHighestDivision, true]
-
A.
higherLevelDivision
Indicates that one administrative or organizational unit is a parent or superior division relative to another, lower-level unit.
-
B.
topDivisionLevel
Indicates that an entity belongs to the highest or primary division level within a hierarchical or organizational structure.
-
C.
topDivisionOf
Indicates that one administrative or organizational unit is the highest-level division within the structure of another entity.
-
D.
topLevelDivisions
Indicates that one administrative or organizational unit is a primary, highest-level subdivision within a larger entity or system.
-
E.
highestLevelAdministrativeDivision
chosen
Indicates that one entity is the topmost (largest or most authoritative) administrative division within the political or territorial hierarchy of the other 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 27, 2026, 2:40 p.m.