Triple
T32967245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adulterers |
E843402
|
entity |
| Predicate | hasFragmentaryEvidence |
P155818
|
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: [The Adulterers, hasFragmentaryEvidence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFragmentaryEvidence Context triple: [The Adulterers, hasFragmentaryEvidence, true]
-
A.
hasFragmentarySurvival
chosen
Indicates that the referenced entity is only partially preserved or survives in an incomplete, fragmentary form.
-
B.
hasMaterialEvidence
Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
-
C.
hasNoEvidenceOf
Indicates that there is no supporting proof, data, or documentation confirming the existence or occurrence of the referenced condition, event, or relationship.
-
D.
hasEvidenceItem
Indicates that there exists a specific piece of evidence supporting, illustrating, or justifying the associated entity or claim.
-
E.
hasEvidentials
Indicates that a statement, claim, or information is accompanied by markers specifying the type or source of evidence supporting it.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:21 a.m.