Triple
T28699815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tim Speedle |
E729517
|
entity |
| Predicate | worksWithEvidenceType |
P3168
|
FINISHED |
| Object | trace evidence |
—
|
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: trace evidence | Statement: [Tim Speedle, worksWithEvidenceType, trace evidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksWithEvidenceType Context triple: [Tim Speedle, worksWithEvidenceType, trace evidence]
-
A.
usedEvidenceType
chosen
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
B.
evidenceTypeHandled
Indicates that an entity is responsible for processing or managing a particular type or category of evidence.
-
C.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
D.
worksAgainst
Indicates that one entity actively opposes, counteracts, or undermines the goals, effects, or interests of another entity.
-
E.
titleEvidenceType
Indicates the type or category of evidence that supports or justifies a given title.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 5:41 a.m.