Triple
T31749031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G16 |
E810356
|
entity |
| Predicate | adjacentCodeBefore |
P94835
|
FINISHED |
| Object | G15 |
—
|
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: G15 | Statement: [G16, adjacentCodeBefore, G15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentCodeBefore Context triple: [G16, adjacentCodeBefore, G15]
-
A.
predecessorCode
chosen
Indicates that one code directly precedes another code in a defined sequence or versioning order.
-
B.
hasAdjacentCodeOnLine
Indicates that one code element is positioned directly next to another on the same line of source code.
-
C.
adjacentCodeDirectionWest
Indicates that one code element is positioned immediately to the west (left) of another code element.
-
D.
adjacentCodeEast
Indicates that one code element is positioned immediately to the east (right side) of another code element.
-
E.
neighboringBlockPrevious
Indicates that one block is adjacent to another block and occurs immediately before it in a defined sequence or ordering.
- 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_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 30, 2026, 11:27 p.m.