Triple
T29442690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belait District |
E746757
|
entity |
| Predicate | wasKeySiteOf |
P161457
|
FINISHED |
| Object | 1962 Brunei Revolt |
—
|
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: 1962 Brunei Revolt | Statement: [Belait District, wasKeySiteOf, 1962 Brunei Revolt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasKeySiteOf Context triple: [Belait District, wasKeySiteOf, 1962 Brunei Revolt]
-
A.
believedToBeSiteOf
Indicates that something is thought or assumed, though not definitively proven, to be the location where a particular event, structure, or phenomenon occurred or existed.
-
B.
isKeySiteOf
chosen
Indicates that a location serves as an important or central place for a particular event, activity, process, or function.
-
C.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
D.
bestKnownAsSiteOf
Indicates that a place is most widely recognized or famous for being the location where a particular event, activity, or feature occurs or is found.
-
E.
significantEventPlace
Indicates the place where a significant event occurred or is associated with an entity.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b1ddb508190bf0a10ffa61bbf5b |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:24 p.m.