Triple
T38091615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fu-Hsing Semi Express |
E951128
|
entity |
| Predicate | successorServiceClass |
P202930
|
FINISHED |
| Object | Tze-Chiang Limited Express |
—
|
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: Tze-Chiang Limited Express | Statement: [Fu-Hsing Semi Express, successorServiceClass, Tze-Chiang Limited Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorServiceClass Context triple: [Fu-Hsing Semi Express, successorServiceClass, Tze-Chiang Limited Express]
-
A.
successorClass
Indicates that one class directly follows or replaces another class in a sequence or hierarchy.
-
B.
successorInterface
Indicates that one interface directly follows and replaces another interface in a sequence or version lineage.
-
C.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
D.
successorClassContext
Indicates that one class serves as the successor or follow-up context to another class within a sequence or hierarchy.
-
E.
successorClassRole
Indicates that one class role directly follows or replaces another class role in a sequence or hierarchy.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00d15f7b788190a3bf440be7837192 |
completed | May 10, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_6a00d0f8ef548190b1c15b06164eec4a |
completed | May 10, 2026, 6:39 p.m. |
| PDg | Predicate description generation | batch_6a00d15e82708190b1246937c695da7e |
completed | May 10, 2026, 6:41 p.m. |
Created at: May 3, 2026, 4:21 p.m.