Triple
T28513743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juba Peace Agreement |
E721559
|
entity |
| Predicate | mediatedInCity |
P166880
|
FINISHED |
| Object | Juba |
—
|
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: Juba | Statement: [Juba Peace Agreement, mediatedInCity, Juba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediatedInCity Context triple: [Juba Peace Agreement, mediatedInCity, Juba]
-
A.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
B.
locatedInCityWithSignificance
Indicates that an entity is located in a city that holds particular importance or notable significance (e.g., historical, cultural, political, or economic).
-
C.
deployedInCity
Indicates that an entity has been placed into active use or operation within a particular city.
-
D.
representedCity
Indicates that an entity serves as the official representative or proxy for a particular city.
-
E.
modeledInCity
Indicates that an entity (such as a model or design) was created, developed, or constructed within a particular city.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 3:15 a.m.