Triple
T8746640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongomo |
E207844
|
entity |
| Predicate | homeRegionOf |
P64798
|
FINISHED |
| Object | much of Equatorial Guinea’s ruling elite |
—
|
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: much of Equatorial Guinea’s ruling elite | Statement: [Mongomo, homeRegionOf, much of Equatorial Guinea’s ruling elite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRegionOf Context triple: [Mongomo, homeRegionOf, much of Equatorial Guinea’s ruling elite]
-
A.
homeCityRegion
Indicates the city or broader regional area that serves as an entity’s primary place of residence or origin.
-
B.
homeConfederationRegion
Indicates the geographic confederation or regional association that serves as the primary home region for an entity.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
placeRegion
chosen
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
E.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d75e7c88190a9e78fadb979e1b6 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.