Triple
T1382488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian integers |
E29369
|
entity |
| Predicate | hasElementForm |
P169
|
FINISHED |
| Object | a+bi with a,b in ℤ and i² = -1 |
—
|
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: a+bi with a,b in ℤ and i² = -1 | Statement: [Gaussian integers, hasElementForm, a+bi with a,b in ℤ and i² = -1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElementForm Context triple: [Gaussian integers, hasElementForm, a+bi with a,b in ℤ and i² = -1]
-
A.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
B.
hasForm
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
C.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
D.
containsForm
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
E.
hasNonStandardForm
Indicates that an entity possesses a form, variant, or representation that deviates from the standard, canonical, or commonly accepted form.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c3361bf08190b3f6bbf82e17685b |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.