Triple
T26176763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IY |
E654563
|
entity |
| Predicate | canBeIncrementedByInstruction |
P75142
|
FINISHED |
| Object | INC IY |
—
|
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: INC IY | Statement: [IY, canBeIncrementedByInstruction, INC IY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeIncrementedByInstruction Context triple: [IY, canBeIncrementedByInstruction, INC IY]
-
A.
hasIncrement
Indicates that one value or state increases by a specified step or amount relative to another.
-
B.
usesIncrement
chosen
Indicates that one entity applies or relies on an increment operation or incremental value derived from another entity.
-
C.
incrementType
Indicates the manner or category by which a value, count, or level is increased from one state to the next.
-
D.
isIncremental
Indicates that something progresses or changes in small, successive steps or increases over time.
-
E.
subsequentIncrease
Indicates that one quantity or value increases after a prior event, state, or change has occurred.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 26, 2026, 8:38 p.m.