Triple
T836370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hashemite dynasty |
E18076
|
entity |
| Predicate | endedRuleInHejaz |
P14957
|
FINISHED |
| Object | 1925 |
—
|
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: 1925 | Statement: [Hashemite dynasty, endedRuleInHejaz, 1925]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedRuleInHejaz Context triple: [Hashemite dynasty, endedRuleInHejaz, 1925]
-
A.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
B.
endRule
chosen
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
C.
notableRule
Indicates that a rule or regulation is particularly significant, prominent, or noteworthy within a given context.
-
D.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
E.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abce08348190b716e3ce5a638f99 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7c7df881909c539c3ab8ff0367 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.