Triple
T33437753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OASIS DITA Technical Committee |
E856273
|
entity |
| Predicate | outputStatus |
P48024
|
FINISHED |
| Object | OASIS Standard |
—
|
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: OASIS Standard | Statement: [OASIS DITA Technical Committee, outputStatus, OASIS Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputStatus Context triple: [OASIS DITA Technical Committee, outputStatus, OASIS Standard]
-
A.
hasOutputStatus
chosen
Indicates that an entity is associated with a particular state or condition of its produced output.
-
B.
returnStatus
Indicates the current outcome or condition of a previously initiated return action or process.
-
C.
programStatus
Indicates the current state or condition of a program within its lifecycle (e.g., planned, active, paused, completed, or terminated).
-
D.
outputIs
Indicates that one entity functions as the result, product, or outcome produced by another entity or process.
-
E.
functionStatus
Indicates the operational state or condition of a function (e.g., active, inactive, pending, or failed) at a given time.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:36 a.m.