Triple
T26894534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samma tribe |
E677863
|
entity |
| Predicate | politicalSystemInDynasty |
P74631
|
FINISHED |
| Object | monarchy |
—
|
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: monarchy | Statement: [Samma tribe, politicalSystemInDynasty, monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalSystemInDynasty Context triple: [Samma tribe, politicalSystemInDynasty, monarchy]
-
A.
governedPolityThroughDynasty
Indicates that a person or group exercised governing authority over a polity specifically by means of holding power within a particular dynasty.
-
B.
rulingDynasties
Indicates that one entity served as the ruling dynasty governing or controlling another entity (such as a state, region, or polity) during a particular historical period.
-
C.
politicalSystemDuringRule
chosen
Indicates the type of political system that was in place during a particular ruler’s period of governance.
-
D.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
E.
reignInDynasty
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 5:47 a.m.