Triple
T5479807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5G NR |
E123441
|
entity |
| Predicate | hasNumerology |
P64029
|
FINISHED |
| Object | scalable OFDM subcarrier spacing |
—
|
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: scalable OFDM subcarrier spacing | Statement: [5G NR, hasNumerology, scalable OFDM subcarrier spacing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumerology Context triple: [5G NR, hasNumerology, scalable OFDM subcarrier spacing]
-
A.
numericalValueInGematria
Indicates that a given entity is associated with a specific numerical value as determined by a gematria system of letter-to-number conversion.
-
B.
numericalValueHebrewGematria
Indicates that a numerical value is assigned to text based on Hebrew gematria, where Hebrew letters correspond to specific numbers and their sum yields the value.
-
C.
numericValueInGematria
Indicates that a given entity is associated with a specific numerical value as determined by the rules of gematria.
-
D.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
E.
hasNumberOfSephirot
Indicates the specific count of sephirot associated with or attributed to an entity.
- F. None of above. chosen
Provenance (4 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd9214b8488190979112c7615f359a |
completed | March 20, 2026, 6:29 p.m. |
Created at: March 20, 2026, 2:09 p.m.