Triple
T32152371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Crawford |
E821192
|
entity |
| Predicate | evidenceAtIssue |
P173817
|
FINISHED |
| Object | recorded statement by Sylvia Crawford |
—
|
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: recorded statement by Sylvia Crawford | Statement: [Michael Crawford, evidenceAtIssue, recorded statement by Sylvia Crawford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evidenceAtIssue Context triple: [Michael Crawford, evidenceAtIssue, recorded statement by Sylvia Crawford]
-
A.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
B.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
C.
evidenceTypeHandled
Indicates that an entity is responsible for processing or managing a particular type or category of evidence.
-
D.
hasMaterialEvidence
Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
-
E.
evidenceCited
Indicates that one entity is used as supporting evidence or citation for the claims or content of another entity.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:31 a.m.