Triple
T35730952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US BPT |
E1032749
|
entity |
| Predicate | codeComponentLocation |
P154388
|
FINISHED |
| Object | BPT |
—
|
NE NERFINISHED |
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: BPT | Statement: [US BPT, codeComponentLocation, BPT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeComponentLocation Context triple: [US BPT, codeComponentLocation, BPT]
-
A.
labelCodePosition
Indicates assigning a specific label to a particular position or location within a code sequence or code structure.
-
B.
documentationLocation
Indicates the place or resource where relevant documentation for an entity can be found.
-
C.
codePlacement
chosen
Indicates the spatial or structural location where a piece of code is inserted, organized, or executed within a larger codebase or system.
-
D.
implementationLocation
Indicates the place or environment where something is implemented, carried out, or put into effect.
-
E.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.