Triple
T4771115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hertz (unit) |
E105928
|
entity |
| Predicate | quantity |
P9758
|
FINISHED |
| Object | frequency |
—
|
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: frequency | Statement: [hertz (unit), quantity, frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quantity Context triple: [hertz (unit), quantity, frequency]
-
A.
usesQuantity
Indicates that one entity employs or applies a specified amount or measure of another entity in performing an action or fulfilling a function.
-
B.
quantityType
chosen
Indicates that one entity is the type or category of quantity to which another entity (a specific measured or measurable amount) belongs.
-
C.
orderQuantity
Indicates the specific amount or number of items requested or scheduled in an order transaction.
-
D.
quantifies
Indicates that one entity expresses or specifies the amount, number, or degree of another entity.
-
E.
quality
Indicates that an entity possesses a particular attribute, characteristic, or degree of excellence that defines how good, suitable, or effective it is in a given context.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655e5dcc8190a932be9b1baaffb2 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.