Triple
T22363347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 功三級金鵄勲章 |
E552834
|
entity |
| Predicate | 対象行為 |
P23475
|
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.
targetBehaviorChange
Indicates a relationship where an intervention or influence is intended to alter, modify, or redirect an entity’s behavior from its current state to a desired new state.
-
B.
behaviorObserved
chosen
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
C.
privateBehavior
Indicates behavior or actions that are intended to be kept confidential, hidden, or restricted from public or general observation.
-
D.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
E.
goalAssociatedWith
Indicates that a goal is connected or linked to another entity, such as an activity, plan, or outcome, in a way that reflects relevance or influence.
- 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.