Triple
T16300949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-S2X |
E395783
|
entity |
| Predicate | usesCoding |
P19896
|
FINISHED |
| Object | LDPC codes |
—
|
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: LDPC codes | Statement: [DVB-S2X, usesCoding, LDPC codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCoding Context triple: [DVB-S2X, usesCoding, LDPC codes]
-
A.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
-
B.
usesCodec
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
-
C.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
D.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
E.
usesLineCode
chosen
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e32da7081908d8bd320374a5731 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.