Triple
T7825981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nose |
E181245
|
entity |
| Predicate | protagonistConcern |
P64698
|
FINISHED |
| Object | size of his nose |
—
|
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: size of his nose | Statement: [The Nose, protagonistConcern, size of his nose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistConcern Context triple: [The Nose, protagonistConcern, size of his nose]
-
A.
narrativeConcern
Indicates a relationship where something is thematically or structurally focused on, revolves around, or is primarily about a particular narrative topic or issue.
-
B.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
C.
targetConcern
chosen
Indicates that something is the specific issue, problem, or subject that is the focus of attention, action, or consideration.
-
D.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
E.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04a6185481908462079bd2827642 |
completed | March 30, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:43 p.m.