Triple
T2155635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labuan |
E47879
|
entity |
| Predicate | establishedAsFederalTerritory |
P35610
|
FINISHED |
| Object | 1984 |
—
|
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: 1984 | Statement: [Labuan, establishedAsFederalTerritory, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsFederalTerritory Context triple: [Labuan, establishedAsFederalTerritory, 1984]
-
A.
federalTerritoryDeclared
chosen
Indicates that a specific area has been officially designated and proclaimed as a federal territory by the relevant national authority.
-
B.
establishedAsAutonomousRegion
Indicates that an area has been formally designated and recognized as an autonomous region with a degree of self-governance.
-
C.
statehoodFrom
Indicates the point in time from which an entity has held official statehood or recognized status as a state.
-
D.
wasUnionTerritoryAs
Indicates that an entity held the status of a union territory during a specified time or under specified conditions.
-
E.
statehoodContext
Indicates the contextual circumstances, conditions, or framework under which an entity’s status as a state (or its statehood) is defined, recognized, or discussed.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe669c188190bb4c1c391ca848b0 |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.