Triple
T32936640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burned |
E842545
|
entity |
| Predicate | hasInvestigationStyle |
P200990
|
FINISHED |
| Object | amateur detective |
—
|
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: amateur detective | Statement: [Burned, hasInvestigationStyle, amateur detective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInvestigationStyle Context triple: [Burned, hasInvestigationStyle, amateur detective]
-
A.
hasInvestmentStyle
Indicates that an entity (such as a fund or portfolio) follows or is characterized by a particular investment style.
-
B.
hasInvestigationTrigger
Indicates that one entity serves as the cause, condition, or event that initiates or justifies an investigation into another entity.
-
C.
hasInvestigationTarget
Indicates that an investigation is directed toward or focused on a particular target entity.
-
D.
hasInvestigationDomain
Indicates that an investigation or inquiry is focused on, or pertains to, a particular subject area or domain.
-
E.
containsInvestigationOf
Indicates that one entity includes or encompasses an investigation or inquiry concerning 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
| PDg | Predicate description generation | batch_69ffc082a4e881908a92313d2c755afe |
completed | May 9, 2026, 11:17 p.m. |
Created at: May 1, 2026, 1:20 a.m.