Triple
T25795901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upongkor |
E649680
|
entity |
| Predicate | isMainPopulationCentreOf |
P110251
|
FINISHED |
| Object | Erromango |
—
|
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: Erromango | Statement: [Upongkor, isMainPopulationCentreOf, Erromango]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainPopulationCentreOf Context triple: [Upongkor, isMainPopulationCentreOf, Erromango]
-
A.
hasPopulationCenter
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
-
B.
isMajorAdministrativeCentre
Indicates that a location functions as the primary hub for governmental and administrative activities within a larger region or jurisdiction.
-
C.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
D.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
E.
isPrimaryPopulatedAreaOf
chosen
Indicates that a populated place is the main or principal inhabited area associated with a larger geographic or administrative 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 6:30 a.m.