Triple
T28746219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Division of the Meritorious Service Cross |
E731379
|
entity |
| Predicate | isNonCombat |
P55953
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Civil Division of the Meritorious Service Cross, isNonCombat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonCombat Context triple: [Civil Division of the Meritorious Service Cross, isNonCombat, true]
-
A.
combatOrNonCombat
Indicates whether an entity is involved in combat activities or is in a non-combat role or situation.
-
B.
nonCombatEquivalentOf
Indicates that one entity serves as the non-combat or peaceful counterpart of another entity that is oriented toward combat or warfare.
-
C.
isCombatUnit
Indicates that an entity functions as a unit specifically designated and equipped to engage in combat operations.
-
D.
isNonCombatDecoration
chosen
Indicates that an award or decoration is given for non-combat service or achievements rather than for participation in direct combat.
-
E.
nonCombatHeroismScope
Indicates the extent or context in which acts of heroism occur outside of direct combat or fighting situations.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:05 a.m.