Triple
T5877255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL-NB |
E130656
|
entity |
| Predicate | hasCodeElement |
P44113
|
FINISHED |
| Object | NB |
—
|
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: NB | Statement: [NL-NB, hasCodeElement, NB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodeElement Context triple: [NL-NB, hasCodeElement, NB]
-
A.
hasProgramElement
chosen
Indicates that one entity contains, includes, or is associated with a specific program element (such as a function, class, module, or code component).
-
B.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
C.
hasCodeContext
Indicates that an entity is associated with or occurs within a particular programming or code-related context.
-
D.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
E.
hasCodeScheme
Indicates that something is associated with or organized according to a particular coding or classification scheme.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.