Triple
T12514663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | printf |
E299164
|
entity |
| Predicate | exitStatus |
P105372
|
FINISHED |
| Object | 0 on success |
—
|
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: 0 on success | Statement: [printf, exitStatus, 0 on success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exitStatus Context triple: [printf, exitStatus, 0 on success]
-
A.
returnStatus
Indicates the current outcome or condition of a previously initiated return action or process.
-
B.
exitTo
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
-
C.
escapeStatus
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
-
D.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
E.
functionStatus
Indicates the operational state or condition of a function (e.g., active, inactive, pending, or failed) at a given time.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954b715fc819091fa84430be46273 |
completed | April 10, 2026, 7:51 p.m. |
Created at: April 8, 2026, 9:57 p.m.