Triple
T24301539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Price |
E606111
|
entity |
| Predicate | assignedLocation |
P155476
|
FINISHED |
| Object | Uganda |
—
|
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: Uganda | Statement: [Elder Price, assignedLocation, Uganda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedLocation Context triple: [Elder Price, assignedLocation, Uganda]
-
A.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
-
B.
plannedLocation
Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
-
C.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
D.
reserveLocation
Indicates that an entity designates or sets aside a specific place for a particular use, purpose, or future activity.
-
E.
locatedOff
Indicates that one entity is situated away from, but in the vicinity of, another entity or reference point, rather than directly on or within it.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f29222d3008190af765d62787ee334 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:09 a.m.