Triple
T28381701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transrapid |
E718905
|
entity |
| Predicate | cannotRunOn |
P31509
|
FINISHED |
| Object | conventional rail tracks |
—
|
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: conventional rail tracks | Statement: [Transrapid, cannotRunOn, conventional rail tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotRunOn Context triple: [Transrapid, cannotRunOn, conventional rail tracks]
-
A.
canRunOn
Indicates that one entity is capable of operating, executing, or functioning on another entity (such as a platform, system, or environment).
-
B.
unsupportedPlatform
chosen
Indicates that a given platform is not supported for a particular action, feature, or system.
-
C.
notSupportedBy
Indicates that an entity does not receive assistance, endorsement, or backing from another entity.
-
D.
cannotTarget
Indicates that one entity is unable or not permitted to select or act upon another entity as a target.
-
E.
cannotBeUsedWithout
Indicates that one entity is dependent on another such that it cannot function, operate, or be utilized unless the other entity is also present or in use.
- 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 1:07 a.m.