Triple
T744440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibadi Islam |
E15310
|
entity |
| Predicate | sharesHistoricalRootsWith |
P3438
|
FINISHED |
| Object | early Kharijites |
—
|
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: early Kharijites | Statement: [Ibadi Islam, sharesHistoricalRootsWith, early Kharijites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesHistoricalRootsWith Context triple: [Ibadi Islam, sharesHistoricalRootsWith, early Kharijites]
-
A.
sharesHistoryWith
chosen
Indicates that two entities have a common or overlapping past, such as shared experiences, events, or origins.
-
B.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
C.
hasHistoricalTieTo
Indicates a relationship where one entity is historically connected or linked to another through past events, associations, or influences.
-
D.
historicallySoughtBy
Indicates that one entity has been actively pursued, desired, or searched for by another entity in the past.
-
E.
historicallyExtendedBy
Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a610ba9881908b4e5e7dcc6ed0f5 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.