Triple
T25493524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Manār Tafsīr |
E638894
|
entity |
| Predicate | compiledAndExpandedBy |
P101708
|
FINISHED |
| Object | Rashid Rida |
—
|
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: Rashid Rida | Statement: [al-Manār Tafsīr, compiledAndExpandedBy, Rashid Rida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compiledAndExpandedBy Context triple: [al-Manār Tafsīr, compiledAndExpandedBy, Rashid Rida]
-
A.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
B.
compiledUnder
Indicates that something (typically code or a program) was built or translated into executable form using a specific compiler, configuration, or compilation environment.
-
C.
compiledTo
Indicates that one artifact (such as source code) has been transformed into another, typically lower-level or executable form, through a compilation process.
-
D.
laterCompiledAs
chosen
Indicates that one work, version, or material was subsequently gathered, edited, or assembled into another compiled work.
-
E.
compiledUnderPatronageOf
Indicates that a work was compiled with the support, sponsorship, or protection of a specific patron.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7a80f9c8190a672355c354e25bf |
completed | May 2, 2026, 1:10 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:39 p.m.