Triple
T33671631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TextWindow object |
E862632
|
entity |
| Predicate | accessedInCodeAs |
P54244
|
FINISHED |
| Object | TextWindow |
—
|
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: TextWindow | Statement: [TextWindow object, accessedInCodeAs, TextWindow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessedInCodeAs Context triple: [TextWindow object, accessedInCodeAs, TextWindow]
-
A.
hasCodeIn
chosen
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
B.
codeUsedBy
Indicates that a specific piece of code is utilized or depended upon by another entity (such as a system, application, or component).
-
C.
alsoAccessibleFrom
Indicates that a location, resource, or entity can be reached or obtained not only from one specified source or path but from an additional source or path as well.
-
D.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
E.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 1:43 a.m.