Triple
T28615556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellipse |
E724264
|
entity |
| Predicate | boundingRectangleDefinedBy |
P14046
|
FINISHED |
| Object | left |
—
|
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: left | Statement: [Ellipse, boundingRectangleDefinedBy, left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundingRectangleDefinedBy Context triple: [Ellipse, boundingRectangleDefinedBy, left]
-
A.
borderDefinedBy
chosen
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
B.
hasBoundaryCoordinates
Indicates that an entity is associated with specific coordinate values that define the limits or outline of its spatial boundary.
-
C.
coordinatesWithin
Indicates that one set of coordinates lies entirely inside the spatial bounds defined by another.
-
D.
enclosesArea
Indicates that one entity surrounds and contains a bounded region of space occupied or defined by another.
-
E.
areaDefinedAs
Indicates that one area is formally specified, delimited, or characterized in terms of another area or defining criteria.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:31 a.m.