Triple
T12350379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daura |
E294467
|
entity |
| Predicate | governingSystemTraditional |
P58791
|
FINISHED |
| Object | emirate system |
—
|
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: emirate system | Statement: [Daura, governingSystemTraditional, emirate system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingSystemTraditional Context triple: [Daura, governingSystemTraditional, emirate system]
-
A.
governedWithinTradition
Indicates that an entity’s actions, decisions, or organization are regulated or constrained according to a particular established tradition or customary framework.
-
B.
mainTradition
chosen
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
C.
laterGoverningSystem
Indicates that one governing system succeeds and replaces another at a later point in time.
-
D.
laterPoliticalSystemUnderRule
Indicates that one political system came under the rule or authority of another political system at a later point in time.
-
E.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7cbff08190849cd2aec4ce3243 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.