Triple
T25426951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MXML |
E637137
|
entity |
| Predicate | typicalRootElement |
P49862
|
FINISHED |
| Object | <Application> |
—
|
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: <Application> | Statement: [MXML, typicalRootElement, <Application>]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRootElement Context triple: [MXML, typicalRootElement, <Application>]
-
A.
baseElement
Indicates that one entity serves as the fundamental or underlying component upon which another entity is built or defined.
-
B.
typicalComponent
Indicates that one entity is a standard or representative component or part of another entity.
-
C.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
-
D.
mainElement
Indicates that one entity is the primary or most important component within another entity or structure.
-
E.
typicalBase
chosen
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 21, 2026, 1:57 p.m.