Triple
T12686059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Wreath of Roses |
E303068
|
entity |
| Predicate | primaryLocationOfAction |
P30151
|
FINISHED |
| Object | summer holiday retreat |
—
|
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: summer holiday retreat | Statement: [A Wreath of Roses, primaryLocationOfAction, summer holiday retreat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLocationOfAction Context triple: [A Wreath of Roses, primaryLocationOfAction, summer holiday retreat]
-
A.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
B.
placeOfMajorReception
Indicates the location where a person or entity received their primary or most significant formal reception, welcome, or honor.
-
C.
primaryLocationOfAppearances
Indicates the main place where an entity most frequently appears or is featured.
-
D.
placeOfEffect
chosen
Indicates the location or setting where an action, event, or effect takes place or is realized.
-
E.
centralLocation
Indicates that one entity serves as the primary or central place 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961d7cd4c81909521839ef5859799 |
completed | April 10, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.