Triple
T28381712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transrapid |
E718905
|
entity |
| Predicate | curveRadiusRequirement |
P51538
|
FINISHED |
| Object | larger than conventional metro systems |
—
|
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: larger than conventional metro systems | Statement: [Transrapid, curveRadiusRequirement, larger than conventional metro systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curveRadiusRequirement Context triple: [Transrapid, curveRadiusRequirement, larger than conventional metro systems]
-
A.
curveRadius
Indicates the radius of curvature associated with an object or path, describing how sharply it bends at a given point.
-
B.
minimumRadiusOfCurves
chosen
Indicates the smallest allowable radius for any curve in a path, track, or route associated with the subject.
-
C.
curvatureCondition
Indicates that a specified geometric object or path satisfies a particular constraint or requirement on its curvature.
-
D.
curveCondition
Indicates that a specific condition or constraint applies to a curve, such as its shape, smoothness, or allowable parameter range.
-
E.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cb6c8708190b0a947d7da770920 |
completed | May 2, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:07 a.m.