Triple
T29348420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DV-5 |
E744234
|
entity |
| Predicate | investigationTrigger |
P103063
|
FINISHED |
| Object | unexplained drops in ore output |
—
|
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: unexplained drops in ore output | Statement: [DV-5, investigationTrigger, unexplained drops in ore output]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigationTrigger Context triple: [DV-5, investigationTrigger, unexplained drops in ore output]
-
A.
investigatedEvent
Indicates that an event was the subject of an investigation or inquiry carried out by some agent.
-
B.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
-
C.
hasInvestigationTrigger
chosen
Indicates that one entity serves as the cause, condition, or event that initiates or justifies an investigation into another entity.
-
D.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
-
E.
helpsInvestigate
Indicates that one entity assists another entity in carrying out an investigation or inquiry.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 2:04 p.m.