Triple
T28381721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transrapid |
E718905
|
entity |
| Predicate | marketAdoptionLevel |
P81258
|
FINISHED |
| Object | limited worldwide |
—
|
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: limited worldwide | Statement: [Transrapid, marketAdoptionLevel, limited worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketAdoptionLevel Context triple: [Transrapid, marketAdoptionLevel, limited worldwide]
-
A.
marketAdoption
Indicates the extent to which a product, service, or innovation has been accepted and used by its target market or customer base.
-
B.
adoptionLevel
chosen
Indicates the degree or extent to which something (such as a product, practice, or technology) has been taken up, accepted, or implemented by its intended users or audience.
-
C.
marketReception
Indicates how a product, service, or work is received, evaluated, and responded to by the market or audience after its introduction.
-
D.
marketLevel
Indicates the relative status or tier of a market in terms of its size, development, or strategic importance.
-
E.
marketUse
Indicates that something is used, applied, or exploited within a market or commercial context.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 1:07 a.m.