Triple
T28381705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transrapid |
E718905
|
entity |
| Predicate | notableCommercialLine |
P202946
|
FINISHED |
| Object | Shanghai Maglev Train |
—
|
NE NERFINISHED |
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: Shanghai Maglev Train | Statement: [Transrapid, notableCommercialLine, Shanghai Maglev Train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCommercialLine Context triple: [Transrapid, notableCommercialLine, Shanghai Maglev Train]
-
A.
notableCommercial
Indicates that an entity is particularly well-known or significant in a commercial context, such as advertising, marketing, or business promotion.
-
B.
notableDeviceLine
Indicates that a device is a prominent or well-known product line associated with an entity.
-
C.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
D.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
E.
notableEnterprise
Indicates that an entity is a business or commercial organization recognized for its significance, prominence, or impact.
- F. None of above. chosen
Provenance (4 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_6a00d508290081909f3d5dfbb2e80c8e |
completed | May 10, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_6a00d49da4cc81909566ad286ec22292 |
completed | May 10, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_6a00d5073e188190b09916119a9c032d |
completed | May 10, 2026, 6:57 p.m. |
Created at: April 28, 2026, 1:07 a.m.