Triple
T32388539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernando Póo Province |
E827603
|
entity |
| Predicate | centralTerritory |
P192386
|
FINISHED |
| Object | Fernando Póo Island |
—
|
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: Fernando Póo Island | Statement: [Fernando Póo Province, centralTerritory, Fernando Póo Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralTerritory Context triple: [Fernando Póo Province, centralTerritory, Fernando Póo Island]
-
A.
missionTerritoryOf
Indicates that a specified territory is under the jurisdiction or scope of a particular mission.
-
B.
homeUnionTerritory
Indicates that a union territory is the primary or official home location associated with an entity.
-
C.
locationUnionTerritory
Indicates that a location is situated within, or is part of, a specific union territory.
-
D.
unionTerritoryWith
Indicates that one entity is a union territory that is administratively associated or linked with another entity.
-
E.
governingUnionTerritory
Indicates that a specified union territory is the administrative jurisdiction governing or responsible for another entity.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: May 1, 2026, 12:52 a.m.