Triple
T25326299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Sarawak |
E635023
|
entity |
| Predicate | recognizedAsIndependentBy |
P359
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Kingdom of Sarawak, recognizedAsIndependentBy, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsIndependentBy Context triple: [Kingdom of Sarawak, recognizedAsIndependentBy, United Kingdom]
-
A.
isIndependent
Indicates that an entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
B.
recognizedAsAutonomousBy
Indicates that one entity formally acknowledges another entity’s status or operation as independent and self-governing.
-
C.
hasIndependent
Indicates that one entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
D.
independenceRecognized
chosen
Indicates that one entity formally acknowledges another entity’s status as independent and self-governing.
-
E.
recognizedAsRepresentativeBy
Indicates that one entity is acknowledged or accepted by another entity as acting as its representative.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:30 p.m.