Triple
T35547025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mei Foo station |
E1027245
|
entity |
| Predicate | hasFormerChineseName |
P196719
|
FINISHED |
| Object | 美孚 |
—
|
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: 美孚 | Statement: [Mei Foo station, hasFormerChineseName, 美孚]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerChineseName Context triple: [Mei Foo station, hasFormerChineseName, 美孚]
-
A.
hasFormerRomanization
Indicates that an entity was previously written or represented using an earlier or superseded system of Romanized spelling.
-
B.
hasChineseNameType
Indicates that an entity’s Chinese name belongs to a particular type or category (e.g., formal, short, transliterated).
-
C.
ChineseNameTraditional
Indicates that an entity’s name is given in traditional Chinese characters.
-
D.
hasEthnonymInChinese
Indicates that an entity has a specific ethnonym (name for an ethnic group or people) expressed in the Chinese language.
-
E.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: May 3, 2026, 4:04 p.m.