Triple
T22363349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 功三級金鵄勲章 |
E552834
|
entity |
| Predicate | 授与条件 |
P122634
|
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: [功三級金鵄勲章, 授与条件, 顕著な戦功]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 授与条件 Context triple: [功三級金鵄勲章, 授与条件, 顕著な戦功]
-
A.
obligationCondition
Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
-
B.
grantingCriteria
chosen
Indicates the conditions or requirements that must be satisfied for something (such as a request, permission, or benefit) to be granted.
-
C.
authorizationCondition
Indicates the specific rules or requirements that must be satisfied for an action or access to be legally or formally authorized.
-
D.
donationCondition
Indicates that a donation is subject to specific terms, requirements, or circumstances that must be met for it to occur or be valid.
-
E.
appointmentCondition
Indicates the specific terms, requirements, or circumstances that must be met or that apply for an appointment to be scheduled, valid, or carried out.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d616748190921bd49039b7f6fc |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.