Triple
T22814096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCDtxStatus |
E565055
|
entity |
| Predicate | "disabled"Meaning |
P28221
|
FINISHED |
| Object | DTX is not used for the encoding |
—
|
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: DTX is not used for the encoding | Statement: [RTCDtxStatus, "disabled"Meaning, DTX is not used for the encoding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: "disabled"Meaning Context triple: [RTCDtxStatus, "disabled"Meaning, DTX is not used for the encoding]
-
A.
deactivated
chosen
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
B.
meaningStatus
Indicates the relationship between an entity and the status of its meaning, such as whether its meaning is defined, clear, ambiguous, or unknown.
-
C.
basicMeaning
Indicates that one entity expresses or conveys the fundamental or core meaning of another entity.
-
D.
duMeaning
Indicates that one entity expresses, conveys, or signifies a particular meaning or sense in relation to another.
-
E.
degMeaning
Indicates that one entity specifies or encodes the meaning or semantic interpretation of another entity.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.