Triple
T18903650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tārīkh al-rusul wa-l-mulūk |
E462397
|
entity |
| Predicate | isMajorSourceFor |
P32799
|
FINISHED |
| Object | early Islamic history |
—
|
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 Islamic history | Statement: [Tārīkh al-rusul wa-l-mulūk, isMajorSourceFor, early Islamic history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorSourceFor Context triple: [Tārīkh al-rusul wa-l-mulūk, isMajorSourceFor, early Islamic history]
-
A.
isMajorSourceOf
chosen
Indicates that one entity serves as a primary or dominant origin, cause, or provider of another entity or effect.
-
B.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
C.
isMajorFor
Indicates that one entity serves as the primary field of academic specialization (major) for another entity, typically a student.
-
D.
hasMainSource
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
E.
isMajorProviderFor
Indicates that one entity serves as a primary or leading supplier or source of goods, services, or resources for another entity.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52b07c08190be0db22826462ae3 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.