Triple
T32740247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GnuCOBOL |
E837198
|
entity |
| Predicate | supportsDialect |
P148226
|
FINISHED |
| Object | IBM COBOL |
E837197
|
NE 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: IBM COBOL | Statement: [GnuCOBOL, supportsDialect, IBM COBOL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDialect Context triple: [GnuCOBOL, supportsDialect, IBM COBOL]
-
A.
usesDialect
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
-
B.
implementsDialectOf
chosen
Indicates that one entity realizes or carries out a specific dialect, variant, or localized form of another entity (such as a language, standard, or protocol).
-
C.
hasDialects
Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
-
D.
haveDialect
Indicates that an entity uses, speaks, or is associated with a particular dialect or regional linguistic variety.
-
E.
hasDialectCounterpart
Indicates that one linguistic form or expression has a corresponding equivalent in another dialect.
- F. None of above.
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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34eff78b44819094fdf8e676b85932 |
completed | June 19, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:12 a.m.