Triple
T6788844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hud |
E155880
|
entity |
| Predicate | savedGroup |
P13546
|
FINISHED |
| Object | believers among ʿĀd |
—
|
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: believers among ʿĀd | Statement: [Hud, savedGroup, believers among ʿĀd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: savedGroup Context triple: [Hud, savedGroup, believers among ʿĀd]
-
A.
saveBy
Indicates that one entity preserves, rescues, or protects another entity from loss, harm, or danger.
-
B.
save
chosen
Indicates preserving or storing something from loss, harm, or use, often for future benefit or protection.
-
C.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
D.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
E.
notableSave
Indicates that an entity is recognized for having made a particularly significant or memorable save (e.g., in a game, match, or critical situation).
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2aa2e0c8190b994261826ae001d |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.