Triple
T6775717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noah |
E155148
|
entity |
| Predicate | savedWith |
P72726
|
FINISHED |
| Object | those who believed with him |
—
|
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: those who believed with him | Statement: [Noah, savedWith, those who believed with him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: savedWith Context triple: [Noah, savedWith, those who believed with him]
-
A.
save
Indicates preserving or storing something from loss, harm, or use, often for future benefit or protection.
-
B.
saveBy
Indicates that one entity preserves, rescues, or protects another entity from loss, harm, or danger.
-
C.
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).
-
D.
reserveLocation
Indicates that an entity designates or sets aside a specific place for a particular use, purpose, or future activity.
-
E.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24f77c88190be21cf4ef132aa31 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d182213c819086fcbbfd3d64d80b |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:13 p.m.