Triple
T230874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWL |
E4407
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | OWL Lite |
E4407
|
NE 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: OWL Lite | Statement: [OWL, hasVersion, OWL Lite]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OWL Lite Context triple: [OWL, hasVersion, OWL Lite]
-
A.
OWL
chosen
OWL (Web Ontology Language) is a W3C-recommended semantic web language used to define and share rich, machine-interpretable ontologies on the web.
-
B.
LTRI
LTRI is a Japanese institution responsible for the professional training and research development of legal professionals, particularly judges and prosecutors.
-
C.
SLD
SLD was a particle physics experiment at the SLAC Linear Collider that made precision measurements of electroweak interactions, including properties of the Z boson.
-
D.
XHTML
XHTML is a reformulation of HTML as an XML-based markup language designed to create structured, standards-compliant web pages.
-
E.
XML Schema
XML Schema is a W3C standard language used to define the structure, content, and data types of XML documents.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25cadae1c8190be0e8dcf33351187 |
completed | Feb. 28, 2026, 3:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a35ea326608190be39ec5260c3dac3 |
completed | Feb. 28, 2026, 9:31 p.m. |
Created at: Feb. 28, 2026, 2:53 a.m.