Triple
T11061646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biliran |
E261520
|
entity |
| Predicate | gainedProvincialStatus |
P73584
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Biliran, gainedProvincialStatus, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedProvincialStatus Context triple: [Biliran, gainedProvincialStatus, 1992]
-
A.
establishedAsProvinceIn
chosen
Indicates that an entity was formally designated or created as a province in a specified year or time period.
-
B.
establishedAsProvincialLegislature
Indicates that an entity has been formally created or designated to function as a provincial-level legislative body.
-
C.
hasProvinceStatus
Indicates that an entity holds the administrative or political status of a province within a larger territorial or governmental system.
-
D.
joinedAsProvince
Indicates that an entity became part of a larger political or administrative unit with the status of a province.
-
E.
succeededToStatehoodAs
Indicates that one entity became a sovereign state as the direct successor to another entity’s prior political or territorial status.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798ea834c819099401e69f995c59f |
completed | April 9, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.