Triple
T27952717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Negative |
E703470
|
entity |
| Predicate | removedVolume |
P164546
|
FINISHED |
| Object | about 240000 tons of rock |
—
|
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: about 240000 tons of rock | Statement: [Double Negative, removedVolume, about 240000 tons of rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedVolume Context triple: [Double Negative, removedVolume, about 240000 tons of rock]
-
A.
removedOn
Indicates that an entity was taken away, deleted, or detached at a specific point in time.
-
B.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
C.
removedAfter
Indicates that one entity is removed or deleted at a point in time that occurs after the removal or deletion of another entity.
-
D.
removedBefore
Indicates that one entity was removed or taken away earlier in time than another specified entity or event.
-
E.
removedPower
Indicates that one entity has taken away or disabled the power, authority, or capability previously held by 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 7:25 p.m.