Triple
T8280571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | people of Lot |
E193658
|
entity |
| Predicate | refusedToRepent |
P59946
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [people of Lot, refusedToRepent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusedToRepent Context triple: [people of Lot, refusedToRepent, true]
-
A.
repentedTo
Indicates that one entity expressed remorse or sought forgiveness directly from another entity.
-
B.
repentedIn
Indicates that an entity has expressed remorse or regret for its actions within a particular context, time, or situation.
-
C.
repudiatedAfter
Indicates that one entity formally rejects, disavows, or withdraws support for another entity after a specified time or subsequent event.
-
D.
refusedAction
chosen
Indicates that an entity deliberately declined or did not agree to perform a specific action requested, expected, or proposed by another entity.
-
E.
ultimatelyRefusesToKill
Indicates that an entity, despite prior opportunity or intent, finally decides not to kill another entity.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ee66e48190af7058b14f3daac9 |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.