Triple
T37404204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomio |
E929077
|
entity |
| Predicate | hasNearbyAdministrativeUnit |
P202583
|
FINISHED |
| Object | East New Britain provincial capital Kokopo |
—
|
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: East New Britain provincial capital Kokopo | Statement: [Pomio, hasNearbyAdministrativeUnit, East New Britain provincial capital Kokopo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyAdministrativeUnit Context triple: [Pomio, hasNearbyAdministrativeUnit, East New Britain provincial capital Kokopo]
-
A.
hasNearbyGeographicalArea
Indicates that one geographical area is located in close spatial proximity to another geographical area.
-
B.
hasNeighbouringAdministrativeUnitType
Indicates that one administrative unit is directly adjacent to another administrative unit of a specified type.
-
C.
hasNearbyCityArea
Indicates that one area is geographically close to or adjacent to a city area.
-
D.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
-
E.
hasNearbyJurisdiction
Indicates that one jurisdiction is geographically close to or adjacent to another jurisdiction.
- F. None of above. chosen
Provenance (4 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a009a0e1fa481909ed881012009b268 |
completed | May 10, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_6a0092e9fcb08190a966d720684f25ec |
completed | May 10, 2026, 2:15 p.m. |
| PDg | Predicate description generation | batch_6a009a0d44b481908285ee39b64cb466 |
completed | May 10, 2026, 2:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.