Triple
T32740266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GnuCOBOL |
E837198
|
entity |
| Predicate | requiresCompiler |
P16200
|
FINISHED |
| Object | C compiler |
—
|
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: C compiler | Statement: [GnuCOBOL, requiresCompiler, C compiler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCompiler Context triple: [GnuCOBOL, requiresCompiler, C compiler]
-
A.
usesCompilerInfrastructure
Indicates that one entity builds upon or relies on another entity’s compiler framework or toolchain to perform its compilation-related tasks.
-
B.
hasCompilerRole
Indicates that an entity serves in the role or function of a compiler for another entity or process.
-
C.
hasMajorCompiler
chosen
Indicates that an entity is associated with or supported by a primary or widely used compiler.
-
D.
requiresCompatibilityWith
Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
-
E.
requiresLanguageVersion
Indicates that one entity depends on or must use a specific version of a language in order to function or be considered valid.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 1, 2026, 1:12 a.m.