Triple
T26541688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Brilliant Star |
E671404
|
entity |
| Predicate | awardedForInChinese |
P125548
|
FINISHED |
| Object | 對國家有特殊勳勞者 |
—
|
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: 對國家有特殊勳勞者 | Statement: [Order of Brilliant Star, awardedForInChinese, 對國家有特殊勳勞者]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedForInChinese Context triple: [Order of Brilliant Star, awardedForInChinese, 對國家有特殊勳勞者]
-
A.
awardNameInTraditionalChinese
chosen
Indicates the traditional Chinese-language name assigned to an award in the relationship.
-
B.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
C.
alsoAwardedIn
Indicates that the same award or recognition was given in an additional time, place, or context beyond the primary one.
-
D.
awardedForToReceive
Indicates that an entity is granted an award or recognition in order to receive it for a specific reason, achievement, or qualifying basis.
-
E.
holderAwardedFor
Indicates that an award holder received the award specifically in recognition of, or as a result of, a particular work, achievement, or contribution.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 1:42 a.m.