Triple
T6344225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HoopoeBirdStory |
E142703
|
entity |
| Predicate | portraysProphetSulaymanAs |
P70095
|
FINISHED |
| Object | wise king |
—
|
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: wise king | Statement: [HoopoeBirdStory, portraysProphetSulaymanAs, wise king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysProphetSulaymanAs Context triple: [HoopoeBirdStory, portraysProphetSulaymanAs, wise king]
-
A.
subjectOfProphecy
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
B.
regardsAsOnlyProphetAfterMoses
Indicates that one entity considers another entity to be the sole legitimate prophet following Moses.
-
C.
regardsAsFinalProphet
Indicates that one entity believes or treats another entity as the ultimate and last prophet, after whom no further prophets will come.
-
D.
prophecyKnownAs
Indicates that a particular prophecy is referred to or recognized by a specific name or title.
-
E.
killedProphetsOf
Indicates that one entity caused the death of prophets who were associated with or sent to another entity.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0674702d08190806ef0998960b797 |
completed | March 22, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:31 p.m.