Triple
T36029012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buy More |
E1042206
|
entity |
| Predicate | primarySettingIn |
P14490
|
FINISHED |
| Object | Chuck |
E151560
|
NE 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: Chuck | Statement: [Buy More, primarySettingIn, Chuck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySettingIn Context triple: [Buy More, primarySettingIn, Chuck]
-
A.
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.
-
B.
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.
-
C.
primarySettingFeature
Indicates that a particular feature is the main or defining characteristic of a setting.
-
D.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
E.
primarySection
Indicates that one entity is the main or most important section or subdivision associated with another entity.
- F. None of above.
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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38d52f6790819089af1b2eefd7c6b8 |
completed | June 22, 2026, 6:24 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.