Triple
T23837094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poincaré coordinates |
E590884
|
entity |
| Predicate | hasRadialCoordinate |
P33954
|
FINISHED |
| Object | z |
—
|
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: z | Statement: [Poincaré coordinates, hasRadialCoordinate, z]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadialCoordinate Context triple: [Poincaré coordinates, hasRadialCoordinate, z]
-
A.
hasPolarRadius
Indicates that an entity possesses a specific radius measured from its center to its pole, typically used for spheroidal or planetary bodies.
-
B.
domainOfRadialCoordinate
chosen
Indicates that a specified set or interval serves as the valid range (domain) of values for a given radial coordinate in a coordinate system.
-
C.
radialExtent
Indicates the radial distance or range over which something extends outward from a central point or axis.
-
D.
isRadialRouteOf
Indicates that one route functions as a radial connection extending outward from a central point, hub, or main route.
-
E.
hasRadialTrendToward
Indicates a relationship in which something exhibits a pattern, orientation, or change that progresses inward toward a central point or axis.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c883c7108190b3cce6fec0b8609a |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:07 p.m.