Triple
T5767694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SVRL |
E127253
|
entity |
| Predicate | hasRootElement |
P66289
|
FINISHED |
| Object | svrl:schematron-output |
—
|
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: svrl:schematron-output | Statement: [SVRL, hasRootElement, svrl:schematron-output]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRootElement Context triple: [SVRL, hasRootElement, svrl:schematron-output]
-
A.
hasWellAtRoot
Indicates that an entity possesses or has a well located at its root or base.
-
B.
hasTextElement
Indicates that an entity contains or is associated with a specific text-based component or segment.
-
C.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
D.
hasProgramElement
Indicates that one entity contains, includes, or is associated with a specific program element (such as a function, class, module, or code component).
-
E.
hasNoChildren
Indicates that the subject entity does not have any children associated with it.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02ac9603481909e3fa295d7904a15 |
completed | March 22, 2026, 5:45 p.m. |
Created at: March 22, 2026, 3:49 p.m.