Triple
T10479638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDT |
E247136
|
entity |
| Predicate | wasUsedToControl |
P49579
|
FINISHED |
| Object | mosquitoes |
—
|
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: mosquitoes | Statement: [DDT, wasUsedToControl, mosquitoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUsedToControl Context triple: [DDT, wasUsedToControl, mosquitoes]
-
A.
usedToControl
chosen
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
B.
usedControl
Indicates that one entity exercised or applied a control mechanism or method over another entity or process.
-
C.
aimsToControl
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
-
D.
affectedControlOf
Indicates that one entity has influenced, altered, or impacted the degree of control another entity has over something.
-
E.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095b2ec881909e1220d83e750a75 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:22 p.m.