Triple
T31744374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-bomber force |
E810228
|
entity |
| Predicate | ValiantRole |
P172496
|
FINISHED |
| Object | initial V-bomber in service |
—
|
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: initial V-bomber in service | Statement: [V-bomber force, ValiantRole, initial V-bomber in service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ValiantRole Context triple: [V-bomber force, ValiantRole, initial V-bomber in service]
-
A.
roleOfWillChampion
Indicates that one entity is the specific role, position, or function held by Will Champion in relation to another entity.
-
B.
roleInKnightfall
Indicates that an entity has a specific role or participation in the context of "Knightfall" (such as a project, event, or production) in relation to another entity.
-
C.
roleInWatchmen
Indicates that one entity has a specific role or function within the context of the work "Watchmen" in relation to the other entity.
-
D.
typeOfBravery
Indicates a specific kind or category of bravery that characterizes an entity’s courageous behavior or action.
-
E.
heroClass
Indicates the character class or role that a hero belongs to within a given system or context.
- F. None of above. chosen
Provenance (4 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:26 p.m.