Triple
T26657419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominic Greene |
E666545
|
entity |
| Predicate | mainSchemeLocation |
P125949
|
FINISHED |
| Object | Bolivia |
—
|
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: Bolivia | Statement: [Dominic Greene, mainSchemeLocation, Bolivia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSchemeLocation Context triple: [Dominic Greene, mainSchemeLocation, Bolivia]
-
A.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
B.
usesScheme
Indicates that one entity employs, follows, or is based on a particular scheme, method, or structured plan associated with another entity.
-
C.
hasScheme
Indicates that one entity is associated with, defined by, or governed through a particular scheme, plan, or structured framework.
-
D.
coreLocation
chosen
Indicates that one entity serves as the central or primary location associated with another entity.
-
E.
metadataLocation
Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
- 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_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 2:35 a.m.