Triple
T36427543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juz 26 |
E897343
|
entity |
| Predicate | totalPartsInWork |
P97683
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [Juz 26, totalPartsInWork, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalPartsInWork Context triple: [Juz 26, totalPartsInWork, 30]
-
A.
numberOfCompletedParts
Indicates the count of parts within a whole that have been finished or fully completed.
-
B.
hasNumberOfPartsInWholeWork
chosen
Indicates that an entity specifies how many component parts are contained within a complete work.
-
C.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
D.
opusNumberOfComponentWork
Indicates that a specific opus number is assigned to a component (sub-)work within a larger musical or artistic work.
-
E.
estimatedWorkingsLength
Indicates the expected or calculated duration or extent of the workings involved in a task, project, or operation.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:10 p.m.