Triple
T34115760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeri Crosby |
E874965
|
entity |
| Predicate | timeSpentInvestigating |
P178246
|
FINISHED |
| Object | over twenty years |
—
|
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: over twenty years | Statement: [Jeri Crosby, timeSpentInvestigating, over twenty years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpentInvestigating Context triple: [Jeri Crosby, timeSpentInvestigating, over twenty years]
-
A.
investigatedAt
Indicates that an investigation into an entity or event took place at a specific location or facility.
-
B.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
C.
areInvestigatedFor
Indicates that one or more entities are the subject of an investigation concerning a particular issue, incident, or alleged wrongdoing.
-
D.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
-
E.
investigate
Indicates that one entity systematically examines, studies, or inquires into another entity or situation to uncover facts or gain understanding.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb880008190bc1ca79d89580949 |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:53 a.m.