Triple
T38677556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sergeant |
E943795
|
entity |
| Predicate | hasMainCharacterRank |
P92230
|
FINISHED |
| Object | non-commissioned officer |
—
|
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: non-commissioned officer | Statement: [The Sergeant, hasMainCharacterRank, non-commissioned officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCharacterRank Context triple: [The Sergeant, hasMainCharacterRank, non-commissioned officer]
-
A.
protagonistRank
chosen
Indicates the relative narrative importance or centrality of a character within a story, typically ranking how primary they are as a protagonist compared to others.
-
B.
hasPrimaryCharacter
Indicates that an entity features another entity as its main or central character.
-
C.
hasMainCharacterFrom
Indicates that a work of fiction has a main character who originates from or belongs to a specified place, group, or source.
-
D.
hasMainProtagonistTrait
Indicates that the specified trait is a defining or primary characteristic of the main protagonist.
-
E.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.