Triple
T7115421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Description Logic |
E165805
|
entity |
| Predicate | typicalReasoningProcedure |
P25044
|
FINISHED |
| Object | tableau-based algorithms |
—
|
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: tableau-based algorithms | Statement: [Description Logic, typicalReasoningProcedure, tableau-based algorithms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalReasoningProcedure Context triple: [Description Logic, typicalReasoningProcedure, tableau-based algorithms]
-
A.
reasoningSummary
Indicates that an entity provides a condensed explanation or overview of the reasoning or logical steps behind a conclusion, decision, or result.
-
B.
hasReasoningTask
Indicates that an entity is associated with, assigned, or involved in a reasoning-related task or activity.
-
C.
typicalConclusion
Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
-
D.
typicalAssumption
Indicates that something is taken as a standard or default assumption that generally holds in typical or normal circumstances.
-
E.
reasoningIncludes
chosen
Indicates that a reasoning process or argument explicitly incorporates or makes use of the referenced element as one of its components or steps.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5f401b881909ef4c2ab1e0750db |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.