Triple
T19155173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunni Islam – Shafi'i school |
E468911
|
entity |
| Predicate | usesSecondarySource |
P38247
|
FINISHED |
| Object | ijma |
—
|
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: ijma | Statement: [Sunni Islam – Shafi'i school, usesSecondarySource, ijma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSecondarySource Context triple: [Sunni Islam – Shafi'i school, usesSecondarySource, ijma]
-
A.
hasSecondarySource
Indicates that an entity is supported, documented, or referenced by a secondary source rather than by a primary or original source.
-
B.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
C.
usesSourceType
chosen
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
D.
secondaryResource
Indicates that a resource serves as a secondary, supporting, or auxiliary resource in relation to a primary one.
-
E.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb914248190a92dc5f30cbc8fcc |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.