Triple
T33324125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | well-maiden |
E853218
|
entity |
| Predicate | consequenceOfNeglect |
P181784
|
FINISHED |
| Object | drying of wells |
—
|
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: drying of wells | Statement: [well-maiden, consequenceOfNeglect, drying of wells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfNeglect Context triple: [well-maiden, consequenceOfNeglect, drying of wells]
-
A.
neglects
Indicates a relationship where one party fails to give appropriate attention, care, or consideration to another party or responsibility.
-
B.
consequenceOfAbuse
Indicates that one situation, condition, or outcome occurs as a direct result of abusive behavior or treatment.
-
C.
fellIntoNeglect
Indicates that something previously maintained or attended to was no longer cared for and gradually deteriorated or was forgotten.
-
D.
consequenceOfChildlessness
Indicates a condition, event, or outcome that arises specifically as a result of being childless.
-
E.
childRestorationConsequence
Indicates the outcome or effect that results from restoring a child entity to a previous or original state.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 1, 2026, 1:33 a.m.