Triple
T2419366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian Order of the Crown |
E52382
|
entity |
| Predicate | militaryDistinction |
P19685
|
FINISHED |
| Object | with Swords |
—
|
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: with Swords | Statement: [Prussian Order of the Crown, militaryDistinction, with Swords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryDistinction Context triple: [Prussian Order of the Crown, militaryDistinction, with Swords]
-
A.
militaryAward
chosen
Indicates that an entity has received or been granted a specific military honor, decoration, or award.
-
B.
battleHonors
Indicates that an entity has been awarded or is associated with specific honors or distinctions earned through participation in battles or military engagements.
-
C.
wartimeAward
Indicates that an entity received an award or honor specifically in the context of wartime or military conflict.
-
D.
peacetimeAward
Indicates that an award or honor is given during a period of peace rather than during wartime or active conflict.
-
E.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.