Triple
T22270300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peraltada corner |
E550456
|
entity |
| Predicate | radiusType |
P57008
|
FINISHED |
| Object | long-radius corner |
—
|
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: long-radius corner | Statement: [Peraltada corner, radiusType, long-radius corner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiusType Context triple: [Peraltada corner, radiusType, long-radius corner]
-
A.
hasRadiusType
chosen
Indicates that an entity has a radius characterized by a specific type or classification.
-
B.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
-
C.
radiusRatio
Indicates the proportional relationship between one radius and another, typically expressing how large one is relative to the other.
-
D.
curveRadius
Indicates the radius of curvature associated with an object or path, describing how sharply it bends at a given point.
-
E.
chargeRadius
Indicates the characteristic radial distance around an entity within which its electric charge or charge-related influence is considered effective.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bf53a481909e2c79de4144f332 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.