Triple
T33182059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tavoyan people |
E849354
|
entity |
| Predicate | historicalNameOfRegion |
P28982
|
FINISHED |
| Object | Tavoy |
—
|
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: Tavoy | Statement: [Tavoyan people, historicalNameOfRegion, Tavoy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameOfRegion Context triple: [Tavoyan people, historicalNameOfRegion, Tavoy]
-
A.
historicalAdministrativeRegionName
Indicates the name assigned to an administrative region as it existed during a specific historical period.
-
B.
historicalRegionNameDerivedFrom
Indicates that the name of a historical region is derived from, or based on, the name of another entity (such as a place, people, or feature).
-
C.
regionHistoricalName
chosen
Indicates that a region has been known by a particular historical name during some past period.
-
D.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
E.
formerNameOfRegion
Indicates that one name was previously used for a region that is now known by a different name.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
Created at: May 1, 2026, 1:29 a.m.