Triple
T7277841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWL 2 EL |
E163073
|
entity |
| Predicate | supportsReasoningTask |
P28755
|
FINISHED |
| Object | subsumption |
—
|
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: subsumption | Statement: [OWL 2 EL, supportsReasoningTask, subsumption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReasoningTask Context triple: [OWL 2 EL, supportsReasoningTask, subsumption]
-
A.
hasReasoningTask
chosen
Indicates that an entity is associated with, assigned, or involved in a reasoning-related task or activity.
-
B.
hasReasoningComplexity
Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
-
C.
supportReasoningProfile
Indicates that one entity provides justification, evidence, or contextual basis for the reasoning profile or inferential behavior associated with another entity.
-
D.
reasoningIncludes
Indicates that a reasoning process or argument explicitly incorporates or makes use of the referenced element as one of its components or steps.
-
E.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.