Triple
T2020018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinar |
E44082
|
entity |
| Predicate | authorityNamedOn |
P34545
|
FINISHED |
| Object | reigning caliph |
—
|
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: reigning caliph | Statement: [Dinar, authorityNamedOn, reigning caliph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityNamedOn Context triple: [Dinar, authorityNamedOn, reigning caliph]
-
A.
designationAuthority
Indicates the entity that has the official power or responsibility to assign, grant, or confer a particular designation to another entity.
-
B.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
C.
legalAuthorityClaimedBy
Indicates that one party asserts or claims to possess legal authority, power, or jurisdiction over another party or matter.
-
D.
originAssociatedWith
Indicates a relationship where an entity is connected to, derived from, or influenced by a particular origin, source, or point of beginning.
-
E.
taxonomicAuthority
Indicates the entity that formally described, named, or classified another entity in a taxonomic context.
- F. None of above. chosen
Provenance (4 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8d0bcbc8190bbbb726ecae1c51b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:38 p.m.