Triple
T19258951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 61131-3 |
E481593
|
entity |
| Predicate | definesLanguage |
P130300
|
FINISHED |
| Object | Ladder Diagram |
—
|
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: Ladder Diagram | Statement: [IEC 61131-3, definesLanguage, Ladder Diagram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesLanguage Context triple: [IEC 61131-3, definesLanguage, Ladder Diagram]
-
A.
definesAPIForLanguage
Indicates that one entity specifies or provides the application programming interface (API) to be used by a particular programming language.
-
B.
RLanguageIs
chosen
Indicates that one entity is the language associated with, used by, or expressed in relation to another entity.
-
C.
isWorkingLanguageOf
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
D.
testLanguage
Indicates that an entity uses or is associated with a particular language for testing or evaluation purposes.
-
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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8752488190ae2dfd2d79373a4b |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.