Triple
T24806187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurwitz quaternions |
E620663
|
entity |
| Predicate | normMap |
P9923
|
FINISHED |
| Object | maps to nonnegative integers |
—
|
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: maps to nonnegative integers | Statement: [Hurwitz quaternions, normMap, maps to nonnegative integers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normMap Context triple: [Hurwitz quaternions, normMap, maps to nonnegative integers]
-
A.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
-
B.
normHierarchy
Indicates a hierarchical relationship between norms, where one norm is ranked as superior, more general, or otherwise governing in relation to another.
-
C.
normDefinedBy
Indicates that a norm, rule, or standard is established, specified, or determined by a particular source or authority.
-
D.
normType
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
-
E.
mapsTo
chosen
Indicates that one entity is associated with or transformed into another entity, typically defining a directional correspondence or function from a source to a target.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.