Triple
T230878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWL |
E4407
|
entity |
| Predicate | serializationFormat |
P1444
|
FINISHED |
| Object | RDF/XML |
—
|
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: RDF/XML | Statement: [OWL, serializationFormat, RDF/XML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serializationFormat Context triple: [OWL, serializationFormat, RDF/XML]
-
A.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
B.
machineReadable
Indicates that something is in a format that can be automatically processed or interpreted by a computer without human intervention.
-
C.
standardFormBasedOn
Indicates that one entity’s standard or canonical form is derived from, defined by, or constructed on the basis of another entity.
-
D.
encodedIn
chosen
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
E.
standardFormBasedIn
Indicates that a standardized form or format is established, defined, or grounded in a particular source, basis, or reference framework.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.