Triple
T26657418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominic Greene |
E666545
|
entity |
| Predicate | mainScheme |
P114887
|
FINISHED |
| Object | seize control of Bolivia's water supply |
—
|
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: seize control of Bolivia's water supply | Statement: [Dominic Greene, mainScheme, seize control of Bolivia's water supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainScheme Context triple: [Dominic Greene, mainScheme, seize control of Bolivia's water supply]
-
A.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
B.
usesScheme
chosen
Indicates that one entity employs, follows, or is based on a particular scheme, method, or structured plan associated with another entity.
-
C.
notableScheme
Indicates that an entity is particularly recognized or prominent within a specific scheme, system, or organizational framework.
-
D.
inSchemeWith
Indicates that two entities are associated with, or categorized under, the same conceptual scheme or classification system.
-
E.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 2:35 a.m.