Triple
T32501170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Companions of the Thicket |
E830664
|
entity |
| Predicate | hasPropheticWarner |
P202888
|
FINISHED |
| Object | Shuayb |
—
|
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: Shuayb | Statement: [Companions of the Thicket, hasPropheticWarner, Shuayb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropheticWarner Context triple: [Companions of the Thicket, hasPropheticWarner, Shuayb]
-
A.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
-
B.
hasPropheticDreams
Indicates that an entity experiences dreams that are believed to foretell or reveal future events.
-
C.
prophecyKnownAs
Indicates that a particular prophecy is referred to or recognized by a specific name or title.
-
D.
prophecyOverheardBy
Indicates that a prophecy was heard or accidentally listened to by a particular entity, without necessarily being its intended recipient.
-
E.
hasPropheticOpponent
Indicates that an entity has an opposing figure who is characterized by making prophecies or predictions about them or their actions.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00cbae75988190974f5b45a2e62326 |
completed | May 10, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_6a00cabe4c5881909cca5efbe494e0d1 |
completed | May 10, 2026, 6:13 p.m. |
| PDg | Predicate description generation | batch_6a00cbad83e88190ba792d3172370f63 |
completed | May 10, 2026, 6:17 p.m. |
Created at: May 1, 2026, 12:59 a.m.