Triple
T26942088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thatta region |
E678546
|
entity |
| Predicate | governedHistoricallyFrom |
P73014
|
FINISHED |
| Object | Thatta |
—
|
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: Thatta | Statement: [Thatta region, governedHistoricallyFrom, Thatta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedHistoricallyFrom Context triple: [Thatta region, governedHistoricallyFrom, Thatta]
-
A.
governedByInPast
Indicates that an entity was under the rule, control, or authority of another entity during a previous time period.
-
B.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
C.
historicalRegionGoverned
Indicates that a subject entity exercised governing authority over a particular historical region during a specified period.
-
D.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
-
E.
historicallyUnderRuleOf
chosen
Indicates that one entity was historically governed, controlled, or ruled by another entity during a past period.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 27, 2026, 6:19 a.m.