Triple
T28615601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LineTo |
E724265
|
entity |
| Predicate | returnsOnSuccess |
P171795
|
FINISHED |
| Object | nonzero |
—
|
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: nonzero | Statement: [LineTo, returnsOnSuccess, nonzero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsOnSuccess Context triple: [LineTo, returnsOnSuccess, nonzero]
-
A.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
-
B.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
-
C.
returnsAs
Indicates that one entity goes back to or resumes a previous state, location, role, or condition associated with another entity.
-
D.
returnStatus
Indicates the current outcome or condition of a previously initiated return action or process.
-
E.
returnsFor
Indicates that an entity goes back to a previous place, state, or counterpart, typically reversing or completing an earlier departure or action.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 28, 2026, 4:31 a.m.