Triple
T21910813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Force Cross |
E541052
|
entity |
| Predicate | typeOfHeroism |
P27803
|
FINISHED |
| Object | extraordinary heroism |
—
|
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: extraordinary heroism | Statement: [Space Force Cross, typeOfHeroism, extraordinary heroism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHeroism Context triple: [Space Force Cross, typeOfHeroism, extraordinary heroism]
-
A.
typeOfBravery
chosen
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
B.
typeOfCharacter
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
C.
heroDepicted
Indicates that one entity is portrayed or represented as a hero in relation to another entity.
-
D.
describesGallantryOf
Indicates a relationship where one entity characterizes, explains, or details the gallant or brave behavior of another entity.
-
E.
heroClass
Indicates the character class or role that a hero belongs to within a given system or context.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121da36e88190b42b82641ec54a19 |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:40 p.m.