Triple
T33625174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Mustadrak ala al-Sahihayn |
E861382
|
entity |
| Predicate | compilerNisba |
P177632
|
FINISHED |
| Object | al-Nishapuri |
—
|
NE NERFINISHED |
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: al-Nishapuri | Statement: [al-Mustadrak ala al-Sahihayn, compilerNisba, al-Nishapuri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilerNisba Context triple: [al-Mustadrak ala al-Sahihayn, compilerNisba, al-Nishapuri]
-
A.
compilerOccupation
Indicates that one entity works as a compiler (e.g., of texts, data, or code) in relation to another entity, typically an organization, project, or work.
-
B.
textCompiler
Indicates that one entity functions as a compiler that processes, transforms, or translates text associated with another entity.
-
C.
compiler
Indicates that one entity serves as a compiler of another, typically transforming source material (such as code or documents) into a compiled or aggregated form.
-
D.
compilerType
Indicates the specific kind or category of compiler associated with or used by an entity.
-
E.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
- F. None of above. chosen
Provenance (4 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:41 a.m.