Triple
T5150701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SI second |
E116185
|
entity |
| Predicate | numericalValueOfTransitionFrequency |
P62234
|
FINISHED |
| Object | 9192631770 |
—
|
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: 9192631770 | Statement: [SI second, numericalValueOfTransitionFrequency, 9192631770]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericalValueOfTransitionFrequency Context triple: [SI second, numericalValueOfTransitionFrequency, 9192631770]
-
A.
typicalFrequencyUnit
Indicates the unit of measurement typically used to express the frequency of an event, action, or occurrence.
-
B.
transmissionFactor
Indicates how strongly or efficiently something is passed or transmitted from one entity to another.
-
C.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
D.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
-
E.
timeUnitOfFrequency
Indicates the unit of time (e.g., day, week, month) in which a given frequency is measured or expressed.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79bf9b088190a556dc02f10204e4 |
completed | March 20, 2026, 4:45 p.m. |
Created at: March 20, 2026, 1:44 p.m.