Triple
T19663515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Suicide Day |
E472141
|
entity |
| Predicate | isObservedByFictionalGroup |
P136864
|
FINISHED |
| Object | residents of Bottom |
—
|
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: residents of Bottom | Statement: [National Suicide Day, isObservedByFictionalGroup, residents of Bottom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isObservedByFictionalGroup Context triple: [National Suicide Day, isObservedByFictionalGroup, residents of Bottom]
-
A.
associatedWithFictionalGroup
Indicates that an entity has a connection or affiliation with a fictional group, organization, or collective.
-
B.
capturedByFictionalGroup
Indicates that an entity is taken prisoner, seized, or otherwise held under the control of a fictional group.
-
C.
usedByFictionalGroup
Indicates that something is utilized or employed by a fictional group or organization within a narrative context.
-
D.
partOfFictionalGroup
Indicates that an entity belongs to or is a member of a specific fictional group, organization, or team.
-
E.
ownedByFictionalCharacter
Indicates that something is possessed or owned by a fictional (not real-world) character.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416671fc81908e25b0477234fa0f |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.