Triple
T33514853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross of Valour (Poland) |
E858338
|
entity |
| Predicate | awardedForContext |
P16522
|
FINISHED |
| Object | combat against an enemy of the state |
—
|
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: combat against an enemy of the state | Statement: [Cross of Valour (Poland), awardedForContext, combat against an enemy of the state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedForContext Context triple: [Cross of Valour (Poland), awardedForContext, combat against an enemy of the state]
-
A.
awardContext
chosen
Indicates the situational or circumstantial context in which an award is given or received.
-
B.
awardedFrom
Indicates that one entity has received an award, prize, or honor that originates from or is granted by another entity.
-
C.
awardedForToReceive
Indicates that an entity is granted an award or recognition in order to receive it for a specific reason, achievement, or qualifying basis.
-
D.
namedForAward
Indicates that an entity is named in honor of a particular award.
-
E.
awardedForMarket
Indicates that an award or recognition is given specifically in relation to a particular market or marketplace.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:39 a.m.