Triple
T26618265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sgt. Fury and his Howling Commandos #1 |
E668124
|
entity |
| Predicate | leadCharacterRole |
P46003
|
FINISHED |
| Object | sergeant |
—
|
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: sergeant | Statement: [Sgt. Fury and his Howling Commandos #1, leadCharacterRole, sergeant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadCharacterRole Context triple: [Sgt. Fury and his Howling Commandos #1, leadCharacterRole, sergeant]
-
A.
leadCharacterCaste
Indicates that the lead character in a work belongs to a specified caste.
-
B.
leadCharacterField
Indicates that one entity serves as the primary or main character associated with another entity, such as a work or production.
-
C.
leadActorRolePattern
Indicates a recurring or characteristic type of role that an actor typically plays as a leading performer in productions.
-
D.
leadCharacterStatus
chosen
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
E.
creditedRoleOf
Indicates that a particular role or position is formally acknowledged as being held or performed by a specific entity in a credit or attribution 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:19 a.m.