Triple
T33474393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molly (New York, I Love You) |
E857279
|
entity |
| Predicate | appearsInSegmentedNarrative |
P144384
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Molly (New York, I Love You), appearsInSegmentedNarrative, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInSegmentedNarrative Context triple: [Molly (New York, I Love You), appearsInSegmentedNarrative, yes]
-
A.
appearsInSegmentOf
chosen
Indicates that one entity occurs within, or is featured as part of, a specific segment or subsection of another entity.
-
B.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
-
C.
hasNarrativeSegments
Indicates that an entity is composed of or associated with multiple distinct narrative segments or sections.
-
D.
appearsInNarrativeStyle
Indicates that one entity is presented or expressed using the narrative style, voice, or storytelling mode associated with another entity.
-
E.
isAnthologySegmentOf
Indicates that one work or segment is a constituent part or episode within a larger anthology 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:38 a.m.