Triple
T26083093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWL 2 DL |
E657899
|
entity |
| Predicate | hasAlternativeProfile |
P165024
|
FINISHED |
| Object | OWL 2 EL |
—
|
NE NERFINISHED |
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: OWL 2 EL | Statement: [OWL 2 DL, hasAlternativeProfile, OWL 2 EL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeProfile Context triple: [OWL 2 DL, hasAlternativeProfile, OWL 2 EL]
-
A.
hasAlternativeProgram
Indicates that one program is an alternative option or substitute for another program.
-
B.
hasAlternativeReferent
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
C.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
D.
hasAlternativeView
Indicates that one entity presents a different or contrasting perspective, interpretation, or representation relative to another entity.
-
E.
hasAlternativeSurface
Indicates that one entity serves as a different or substitute surface option for 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 26, 2026, 7:40 p.m.