Triple
T20367681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerry (The Zoo Story) |
E496956
|
entity |
| Predicate | primarySettingOfAction |
P14490
|
FINISHED |
| Object | park bench |
—
|
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: park bench | Statement: [Jerry (The Zoo Story), primarySettingOfAction, park bench]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySettingOfAction Context triple: [Jerry (The Zoo Story), primarySettingOfAction, park bench]
-
A.
primarySettingOf
chosen
Indicates that a location or context serves as the main or principal setting in which an entity (such as a story, event, or activity) takes place.
-
B.
primarySetting
Indicates that one entity serves as the main or central location, context, or environment in which the other entity’s events or activities primarily take place.
-
C.
primarySettingFeature
Indicates that a particular feature is the main or defining characteristic of a setting.
-
D.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
-
E.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6787291d88190a526fe2461d2a7c6 |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:26 a.m.