Triple
T32249846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRIMOS |
E823850
|
entity |
| Predicate | hasProgrammingEnvironment |
P192075
|
FINISHED |
| Object | FORTRAN |
—
|
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: FORTRAN | Statement: [PRIMOS, hasProgrammingEnvironment, FORTRAN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgrammingEnvironment Context triple: [PRIMOS, hasProgrammingEnvironment, FORTRAN]
-
A.
hasSoftwareEnvironment
chosen
Indicates that an entity is associated with, or operates within, a particular software environment or configuration.
-
B.
hasLanguageOfProgramming
Indicates that an entity uses, is implemented in, or is otherwise associated with a particular programming language.
-
C.
hasProgrammingScope
Indicates that something (such as a role, task, or activity) involves or includes programming-related responsibilities or subject matter.
-
D.
hasComputerPrograms
Indicates that one entity possesses, contains, or is associated with one or more computer programs.
-
E.
hasProgrammingDomain
Indicates that an entity is associated with or specializes in a particular programming domain or area of software development.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: May 1, 2026, 12:40 a.m.