Triple
T30327333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle Limit I |
E771376
|
entity |
| Predicate | shapeOfBoundary |
P76137
|
FINISHED |
| Object | circle |
—
|
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: circle | Statement: [Circle Limit I, shapeOfBoundary, circle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shapeOfBoundary Context triple: [Circle Limit I, shapeOfBoundary, circle]
-
A.
hasBoundaryShape
chosen
Indicates that an entity is associated with, or characterized by, a specific geometric or spatial shape of its boundary.
-
B.
outerBoundary
Indicates that one entity serves as the enclosing outer limit or perimeter that bounds another entity or region.
-
C.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for another entity.
-
D.
boundaryBasis
Indicates that one entity serves as a foundational or defining boundary for another entity.
-
E.
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.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681c48ffc819098fa0303a15f2114 |
completed | May 2, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:53 p.m.