Triple
T19156596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masisi Territory |
E468941
|
entity |
| Predicate | conflictAffectedSince |
P28865
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Masisi Territory, conflictAffectedSince, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictAffectedSince Context triple: [Masisi Territory, conflictAffectedSince, 1990s]
-
A.
conflictBeganInYear
Indicates that the specified conflict started or first broke out in the given calendar year.
-
B.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
C.
conflictStartTime
Indicates the specific point in time at which a conflict between entities begins.
-
D.
conflictBeganOver
Indicates that a conflict was initiated due to or in response to a particular cause, issue, or trigger.
-
E.
hasMonthOfConflict
Indicates that a conflict is associated with, occurs in, or is characterized by a specific calendar month.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb9cf9081908b17073755e83554 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.