Triple
T23837095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poincaré coordinates |
E590884
|
entity |
| Predicate | hasBoundaryCoordinates |
P153811
|
FINISHED |
| Object | x^{ mu} |
—
|
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: x^{
mu} | Statement: [Poincaré coordinates, hasBoundaryCoordinates, x^{
mu}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoundaryCoordinates
Context triple: [Poincaré coordinates, hasBoundaryCoordinates, x^{
mu}]
-
A.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
B.
hasBoundaryShape
Indicates that an entity is associated with, or characterized by, a specific geometric or spatial shape of its boundary.
-
C.
hasBoundaryIncludes
Indicates that the spatial or conceptual boundary of one entity encompasses or contains the boundary of another entity.
-
D.
hasBoundaryValues
Indicates that one entity specifies the limiting or extreme values that define the permissible range or boundary conditions of another entity.
-
E.
hasBoundaryCriterion
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
- 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_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. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8:07 p.m.