Triple
T34824407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kono people |
E1003875
|
entity |
| Predicate | civilWarFactor |
P70835
|
FINISHED |
| Object | conflict over diamond resources |
—
|
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: conflict over diamond resources | Statement: [Kono people, civilWarFactor, conflict over diamond resources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilWarFactor Context triple: [Kono people, civilWarFactor, conflict over diamond resources]
-
A.
civilWarPeriod
Indicates a time span during which a civil war is occurring or in effect.
-
B.
civilWarSignificance
chosen
Indicates the importance or impact that a particular entity, event, or factor has within the context of a civil war.
-
C.
hasCivilWarAssociation
Indicates a relationship in which an entity is connected or related to a civil war, such as through involvement, impact, or relevance.
-
D.
civilWarStart
Indicates the point in time or event at which an internal armed conflict between factions of the same state or society begins.
-
E.
civilWarTheater
Indicates a geographic or operational area where events of a civil war take place or are focused.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4 p.m.