Triple
T27585343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VisualAge Pacbase |
E699677
|
entity |
| Predicate | programmingLanguageTarget |
P168086
|
FINISHED |
| Object | COBOL |
—
|
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: COBOL | Statement: [VisualAge Pacbase, programmingLanguageTarget, COBOL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingLanguageTarget Context triple: [VisualAge Pacbase, programmingLanguageTarget, COBOL]
-
A.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
B.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
C.
compilerLanguage
Indicates that one entity is the programming language in which a given compiler is implemented.
-
D.
programTarget
Indicates that a program or initiative is directed toward, intended for, or focused on a particular target entity.
-
E.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
- F. None of above. chosen
Provenance (4 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 27, 2026, 2:04 p.m.