Triple
T26427243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWL Working Group |
E664401
|
entity |
| Predicate | outputDocumentType |
P18123
|
FINISHED |
| Object | W3C Proposed Recommendation |
—
|
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: W3C Proposed Recommendation | Statement: [OWL Working Group, outputDocumentType, W3C Proposed Recommendation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputDocumentType Context triple: [OWL Working Group, outputDocumentType, W3C Proposed Recommendation]
-
A.
DOCType
Indicates the type or category of a document associated with an entity or action.
-
B.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
C.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
D.
documentTypeProduced
chosen
Indicates that one entity produces, generates, or creates a document of a specified type.
-
E.
worksOnDocumentType
Indicates that an entity is involved in handling, processing, or performing tasks related to a specific type or category of document.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 11:46 p.m.