Triple
T8939312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luqman |
E212856
|
entity |
| Predicate | centralThemeOfNarrative |
P56597
|
FINISHED |
| Object | wisdom as a divine favor |
—
|
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: wisdom as a divine favor | Statement: [Luqman, centralThemeOfNarrative, wisdom as a divine favor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralThemeOfNarrative Context triple: [Luqman, centralThemeOfNarrative, wisdom as a divine favor]
-
A.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
-
B.
narrativeMotif
Indicates a recurring thematic element, pattern, or situation that appears across one or more narratives and helps structure or convey their underlying meanings.
-
C.
narrativeThemeInvolvement
Indicates that an entity participates in or contributes to a particular narrative theme within a story or discourse.
-
D.
narrativeSubject
Indicates that an entity functions as the main subject or focal point within a narrative or story.
-
E.
centralThemeContext
chosen
Indicates that one concept serves as the main thematic focus within the situational, narrative, or discourse context defined by another.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b7484481909e0d7610552f5386 |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.