Triple
T2691435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Majuro |
E58409
|
entity |
| Predicate | hasISO3166-2 |
P9401
|
FINISHED |
| Object | MH-L |
—
|
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: MH-L | Statement: [Majuro, hasISO3166-2, MH-L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO3166-2 Context triple: [Majuro, hasISO3166-2, MH-L]
-
A.
isInUnitedStatesMunicipalHierarchy
Indicates that one administrative or governmental unit occupies a specific level or position within the municipal hierarchy of the United States (e.g., city, town, county, or similar local jurisdiction).
-
B.
hasSubnationalCounterpart
Indicates that an entity has a corresponding or equivalent entity at a lower (subnational) administrative level.
-
C.
hasHigherLevelSubdivision
Indicates that one administrative or organizational unit is contained within and subordinate to a larger, higher-level subdivision.
-
D.
countrySubdivision
Indicates that one geopolitical region is an administrative or territorial subdivision of a larger country.
-
E.
countrySubdivisionStandardLink
chosen
Indicates a reference or link to the standard or authoritative specification that defines the country’s internal subdivisions.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0cb9b48190ab354c277cef9e23 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.