Triple
T29267939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lembaga (clan chief) |
E742026
|
entity |
| Predicate | roleInDisputes |
P105905
|
FINISHED |
| Object | mediates intra-clan disputes |
—
|
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: mediates intra-clan disputes | Statement: [Lembaga (clan chief), roleInDisputes, mediates intra-clan disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDisputes Context triple: [Lembaga (clan chief), roleInDisputes, mediates intra-clan disputes]
-
A.
disputeSettlementRole
chosen
Indicates the specific function or capacity an entity assumes in the process of resolving or settling a dispute.
-
B.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
C.
statusDisputedBy
Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
-
D.
laterDisputedBy
Indicates that a previously made claim, statement, or assertion is subsequently challenged, questioned, or contradicted by another party.
-
E.
disputeIssue
Indicates that there is a disagreement or conflict specifically concerning a particular issue or point of contention.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: April 28, 2026, 12:46 p.m.