Triple
T28381707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transrapid |
E718905
|
entity |
| Predicate | commercialOperatorCountry |
P52713
|
FINISHED |
| Object | China |
—
|
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: China | Statement: [Transrapid, commercialOperatorCountry, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialOperatorCountry Context triple: [Transrapid, commercialOperatorCountry, China]
-
A.
publicTelecomOperator
Indicates that an entity functions as a telecommunications service provider that is publicly owned, controlled, or designated to operate in the public interest.
-
B.
commercialOperator
chosen
Indicates that an entity operates or manages a commercial activity, service, or facility, typically for profit or business purposes.
-
C.
refersToCountryOfOperator
Indicates that something is associated with, or points to, the country where its operating organization or operator is based.
-
D.
mobileCountryCode
Indicates the numerical code that identifies the country associated with a mobile network or subscriber.
-
E.
operatedByCountry
Indicates that an entity (such as an organization, facility, or service) is run, managed, or controlled by a specific country or its government.
- 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_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 1:07 a.m.