Triple
T25022196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'll Be Seeing You |
E626605
|
entity |
| Predicate | maleLeadCharacterCondition |
P157910
|
FINISHED |
| Object | shell shock |
—
|
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: shell shock | Statement: [I'll Be Seeing You, maleLeadCharacterCondition, shell shock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maleLeadCharacterCondition Context triple: [I'll Be Seeing You, maleLeadCharacterCondition, shell shock]
-
A.
femaleLeadCharacterStatus
Indicates the narrative or role status assigned to a female lead character within a story or production.
-
B.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
C.
hasLeadCharacterGender
Indicates that the primary or lead character in a work has a specified gender.
-
D.
hasProtagonistCondition
Indicates that the main character in a narrative has a particular condition, state, or affliction.
-
E.
isMaleCharacter
Indicates that the referenced character is identified as male.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:07 a.m.