Triple
T19607251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weekend in New England |
E470637
|
entity |
| Predicate | hasKeyMood |
P7863
|
FINISHED |
| Object | nostalgic |
—
|
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: nostalgic | Statement: [Weekend in New England, hasKeyMood, nostalgic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyMood Context triple: [Weekend in New England, hasKeyMood, nostalgic]
-
A.
hasMood
chosen
Indicates that an entity is experiencing or characterized by a particular emotional or affective state.
-
B.
hasMoodCategory
Indicates that an entity is associated with a particular mood classification or emotional category.
-
C.
hasMoodSystem
Indicates that an entity possesses or is associated with a system responsible for managing or representing moods or emotional states.
-
D.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
E.
hasKeyMovement
Indicates that one entity possesses or defines the primary or characteristic movement pattern associated with another entity.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640c8aae8819086337e364724f1cb |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.