Triple
T28381724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transrapid |
E718905
|
entity |
| Predicate | keyDisadvantage |
P7153
|
FINISHED |
| Object | high infrastructure cost |
—
|
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: high infrastructure cost | Statement: [Transrapid, keyDisadvantage, high infrastructure cost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyDisadvantage Context triple: [Transrapid, keyDisadvantage, high infrastructure cost]
-
A.
disadvantage
Indicates that one entity is in a less favorable, weaker, or hindered position relative to another in a given context.
-
B.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
C.
keyPower
Indicates that an entity possesses a primary or controlling power, authority, or influence over another entity or process.
-
D.
keyDemand
Indicates that one entity requests or requires another entity to provide or use a specific key (such as a cryptographic or access key).
-
E.
keyFeature
chosen
Indicates that something is a primary, distinguishing, or most important feature of an entity.
- 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.