Triple
T2384484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPENSTEP |
E46387
|
entity |
| Predicate | supportsGUIProgramming |
P35060
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [OPENSTEP, supportsGUIProgramming, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGUIProgramming Context triple: [OPENSTEP, supportsGUIProgramming, true]
-
A.
supportedParadigm
Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
-
B.
supportsProgramType
chosen
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
C.
developedWith
Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
-
D.
programUsed
Indicates that a particular program, software, or application was employed or utilized in performing an action or achieving a result.
-
E.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7bc87d0819090cd9d19d748bcc3 |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.