Triple
T13019609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TMainMenu |
E322639
|
entity |
| Predicate | runTimeSupport |
P107481
|
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: [TMainMenu, runTimeSupport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runTimeSupport Context triple: [TMainMenu, runTimeSupport, true]
-
A.
originalRuntime
Indicates the initial or primary duration associated with something, typically before any edits, changes, or adjustments are made.
-
B.
primaryRuntime
Indicates the main runtime environment or platform under which an entity (such as a program, service, or component) is intended to execute.
-
C.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
D.
usesLanguageRuntime
Indicates that an entity operates using, depends on, or is executed within a specific language runtime environment.
-
E.
frameworkSupport
Indicates that one entity provides compatibility with, or operational support for, a particular framework used by another entity.
- F. None of above. chosen
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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecf21bc819082fb512bc479b4be |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:51 p.m.