Triple
T21192740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NR |
E522250
|
entity |
| Predicate | supportsNumerology |
P143501
|
FINISHED |
| Object | subcarrier spacing 15 kHz |
—
|
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: subcarrier spacing 15 kHz | Statement: [NR, supportsNumerology, subcarrier spacing 15 kHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNumerology Context triple: [NR, supportsNumerology, subcarrier spacing 15 kHz]
-
A.
hasNumerology
Indicates a relationship where a numerological value, interpretation, or system is associated with an entity.
-
B.
hasNumeral
Indicates that one entity is associated with a numeral representation or numeric symbol of another entity.
-
C.
usesNumeralsFrom
Indicates that one writing system, notation, or representation employs the numeral symbols originating from another system.
-
D.
hasUseInNumerals
Indicates that something is employed or functions as a component within numeral systems or numerical representations.
-
E.
hasSacredNumber
Indicates that a particular number is regarded as sacred, holy, or spiritually significant in relation 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73338dbe881908360dedad65c964b |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:07 p.m.