Triple
T836391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hashemite dynasty |
E18076
|
entity |
| Predicate | arabRevoltLeadershipStart |
P4699
|
FINISHED |
| Object | 1916 |
—
|
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: 1916 | Statement: [Hashemite dynasty, arabRevoltLeadershipStart, 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arabRevoltLeadershipStart Context triple: [Hashemite dynasty, arabRevoltLeadershipStart, 1916]
-
A.
associatedCaliph
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
-
B.
uprisingDate
chosen
Indicates the date on which an uprising or rebellion occurred or began.
-
C.
belligerentLeader
Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
-
D.
militaryLeader
Indicates that one entity serves as the commanding military leader of another entity, such as a state, organization, or armed force.
-
E.
civilWarStart
Indicates the point in time or event at which an internal armed conflict between factions of the same state or society begins.
- 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.