Triple
T28400321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synchronous Digital Hierarchy |
E719378
|
entity |
| Predicate | hasBasicRate |
P81487
|
FINISHED |
| Object | STM-1 |
—
|
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: STM-1 | Statement: [Synchronous Digital Hierarchy, hasBasicRate, STM-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasicRate Context triple: [Synchronous Digital Hierarchy, hasBasicRate, STM-1]
-
A.
baseRate
chosen
Indicates the fundamental or standard rate at which something occurs or is charged, serving as a baseline before adjustments or modifiers are applied.
-
B.
hasBasePlan
Indicates that an entity is associated with or derived from a specified foundational or default plan.
-
C.
hasRateType
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
-
D.
typicalRate
Indicates the standard or commonly expected rate at which something occurs, is charged, or is applied in a given context.
-
E.
hasBasicUnit
Indicates that one entity is composed of, defined by, or fundamentally characterized through another entity that serves as its basic or minimal unit.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 1:19 a.m.