Triple
T4771253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertzian waves |
E105930
|
entity |
| Predicate | unitNameAssociation |
P12481
|
FINISHED |
| Object | hertz (Hz) |
—
|
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: hertz (Hz) | Statement: [Hertzian waves, unitNameAssociation, hertz (Hz)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitNameAssociation Context triple: [Hertzian waves, unitNameAssociation, hertz (Hz)]
-
A.
associatedWithUnit
chosen
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
B.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
C.
primaryUniformAssociation
Indicates that one entity is designated as the main or primary uniform associated with another entity.
-
D.
unitNamePlural
Indicates the plural form of the name used to refer to a particular unit.
-
E.
unitsFormGroupIsomorphicTo
Indicates that the group formed by the units (invertible elements) of one algebraic structure is isomorphic, as a group, to the group formed by the units of another structure.
- 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.