Triple
T31749032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G16 |
E810356
|
entity |
| Predicate | adjacentCodeAfter |
P94834
|
FINISHED |
| Object | G17 |
—
|
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: G17 | Statement: [G16, adjacentCodeAfter, G17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentCodeAfter Context triple: [G16, adjacentCodeAfter, G17]
-
A.
adjacentCodeEast
Indicates that one code element is positioned immediately to the east (right side) of another code element.
-
B.
successorCode
chosen
Indicates that one code directly follows and replaces another code in a defined sequence or versioning scheme.
-
C.
hasAdjacentCodeOnLine
Indicates that one code element is positioned directly next to another on the same line of source code.
-
D.
adjacentCodeDirectionWest
Indicates that one code element is positioned immediately to the west (left) of another code element.
-
E.
adjacentLine
Indicates that one line is directly next to another line, sharing a common boundary or position without overlapping.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 30, 2026, 11:27 p.m.