Triple
T25082261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultanate of Brunei authority in Sarawak |
E628215
|
entity |
| Predicate | affectedPeoples |
P56117
|
FINISHED |
| Object | Malay communities in Sarawak |
—
|
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: Malay communities in Sarawak | Statement: [Sultanate of Brunei authority in Sarawak, affectedPeoples, Malay communities in Sarawak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedPeoples Context triple: [Sultanate of Brunei authority in Sarawak, affectedPeoples, Malay communities in Sarawak]
-
A.
affectedPeople
chosen
Indicates the people who are impacted or influenced by a particular event, action, or condition.
-
B.
estimatedAffectedPeople
Indicates the estimated number of people expected to be impacted by a particular event, condition, or action.
-
C.
affectedPerson
Indicates that a particular person is impacted or influenced by an event, action, or condition.
-
D.
affectedCountry
Indicates that a particular country is impacted or influenced by an event, action, or condition.
-
E.
impactOnHumans
Indicates a relationship where something produces an effect, influence, or consequence on humans.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:22 a.m.