Triple
T1382515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian integers |
E29369
|
entity |
| Predicate | distanceMetric |
P27195
|
FINISHED |
| Object | induced by complex absolute value |
—
|
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: induced by complex absolute value | Statement: [Gaussian integers, distanceMetric, induced by complex absolute value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceMetric Context triple: [Gaussian integers, distanceMetric, induced by complex absolute value]
-
A.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
B.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
cityBlock
Indicates that one entity is a city block that contains, is the location of, or is otherwise spatially associated with the other entity.
-
D.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
E.
distanceCategory
Indicates the qualitative classification of how far apart two entities are from each other (e.g., near, medium, far).
- 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_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. |
| PDg | Predicate description generation | batch_69a4c0335f7081908d50046ced4cdee0 |
completed | March 1, 2026, 10:39 p.m. |
Created at: March 1, 2026, 7:59 p.m.