Triple
T36468978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poincaré metric |
E898491
|
entity |
| Predicate | hasLineElementOnUpperHalfPlane |
P160154
|
FINISHED |
| Object | |dz|^2/(Im z)^2 |
—
|
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: |dz|^2/(Im z)^2 | Statement: [Poincaré metric, hasLineElementOnUpperHalfPlane, |dz|^2/(Im z)^2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineElementOnUpperHalfPlane Context triple: [Poincaré metric, hasLineElementOnUpperHalfPlane, |dz|^2/(Im z)^2]
-
A.
extendsAboveBelowPlane
Indicates that an object spans across a reference plane, with portions extending both above and below that plane.
-
B.
hasRailLineAbove
Indicates that one rail line is physically located above another rail line, such as on an overpass or elevated structure.
-
C.
actionTypeOnUpperHalfPlane
chosen
Indicates that the action or operation is specifically applied to, or takes place within, the upper half of the complex plane.
-
D.
intersectsXAxisAt
Indicates that a geometric object crosses or touches the x-axis at one or more specific points.
-
E.
hasSecondLineUpperLevel
Indicates that an entity possesses a second line located on an upper level or tier relative to a primary or lower line.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 3, 2026, 4:10 p.m.