Triple
T26176699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF |
E654561
|
entity |
| Predicate | usedByInstruction |
P168560
|
FINISHED |
| Object | ADD A,r |
—
|
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: ADD A,r | Statement: [AF, usedByInstruction, ADD A,r]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByInstruction Context triple: [AF, usedByInstruction, ADD A,r]
-
A.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
B.
usedByProgram
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
-
C.
usedByLine
Indicates that something (such as a resource, tool, or component) is utilized or operated by a particular line (for example, a production line, transit line, or code line).
-
D.
usedByBranch
Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
-
E.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 26, 2026, 8:38 p.m.