Triple
T31770948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOCAL monitor systems |
E810936
|
entity |
| Predicate | designedForProgrammingLanguage |
P75919
|
FINISHED |
| Object | FOCAL |
—
|
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: FOCAL | Statement: [FOCAL monitor systems, designedForProgrammingLanguage, FOCAL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForProgrammingLanguage Context triple: [FOCAL monitor systems, designedForProgrammingLanguage, FOCAL]
-
A.
developedForLanguage
chosen
Indicates that something (such as a tool, system, or resource) was specifically created or adapted to be used with a particular language.
-
B.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
C.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
D.
programmingLanguageTarget
Indicates that one entity is the target or intended implementation language for programming-related work associated with another entity.
-
E.
languageDesigned
Indicates that one entity created or developed the language used or associated with another entity.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 30, 2026, 11:33 p.m.