Triple
T27952710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Negative |
E703470
|
entity |
| Predicate | cutInto |
P163804
|
FINISHED |
| Object | edge of Mormon Mesa |
—
|
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: edge of Mormon Mesa | Statement: [Double Negative, cutInto, edge of Mormon Mesa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cutInto Context triple: [Double Negative, cutInto, edge of Mormon Mesa]
-
A.
cutBy
Indicates that one entity is divided, severed, or shaped as a result of another entity performing a cutting action on it.
-
B.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
-
C.
cuttingResultedIn
Indicates that an act of cutting caused or produced a particular outcome, state, or resulting object.
-
D.
cutter
Indicates that an entity is used to cut or divide another entity.
-
E.
cutOff
Indicates that one entity causes another entity to be disconnected, interrupted, or severed from a source, flow, or continuation.
- 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_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 7:25 p.m.