Triple
T17612373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | healing of Naaman |
E428993
|
entity |
| Predicate | numberOfWashings |
P128283
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [healing of Naaman, numberOfWashings, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfWashings Context triple: [healing of Naaman, numberOfWashings, 7]
-
A.
isRinseRequired
Indicates that an item or surface must be rinsed, typically with water, as a required step in a process or procedure.
-
B.
hasWashStills
Indicates that an entity possesses or is equipped with wash stills used in distillation.
-
C.
wornUntil
Indicates that an item of clothing or wearable object was used or worn continuously up to a specific time or event.
-
D.
usesWashbacks
Indicates that one entity employs or applies washbacks (such as feedback or consequential effects) in relation to another entity or process.
-
E.
hasWashbacksMaterial
Indicates that an entity is associated with or contains material used for washbacks (e.g., components, substances, or resources involved in a washing or backwash process).
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2eaa348190a8226eef8c0d6e31 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:51 a.m.