Triple
T24474111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terengganu Sultanate |
E617181
|
entity |
| Predicate | recognizedAsMalayState |
P156242
|
FINISHED |
| Object | British Malaya |
—
|
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: British Malaya | Statement: [Terengganu Sultanate, recognizedAsMalayState, British Malaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsMalayState Context triple: [Terengganu Sultanate, recognizedAsMalayState, British Malaya]
-
A.
regionInMalaysia
Indicates that a region or area is located within the country of Malaysia.
-
B.
nearestMalaysianState
Indicates the relationship where a given location is associated with the Malaysian state that is geographically closest to it.
-
C.
hasFederalTerritory
Indicates that a sovereign state possesses and administers one or more territories directly under its federal authority rather than as constituent states or provinces.
-
D.
statusInMalaysia
Indicates the legal, social, or official standing or condition an entity holds specifically within the context of Malaysia.
-
E.
officialNameMalay
Indicates the name officially used for something in the Malay language.
- F. None of above. chosen
Provenance (4 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299457ce081909e8d95fd482928dc |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.