Triple
T32543615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sullivan Entertainment |
E831781
|
entity |
| Predicate | settingCommonlyUsed |
P15599
|
FINISHED |
| Object | Prince Edward Island |
—
|
NE NERFINISHED |
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: Prince Edward Island | Statement: [Sullivan Entertainment, settingCommonlyUsed, Prince Edward Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingCommonlyUsed Context triple: [Sullivan Entertainment, settingCommonlyUsed, Prince Edward Island]
-
A.
frequentSettingType
Indicates that an entity commonly or regularly occurs, operates, or is used in a particular type of setting or environment.
-
B.
frequentlyUsedBy
Indicates that something is regularly or commonly utilized by a particular entity.
-
C.
usedAsSettingFor
chosen
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
-
D.
settingChange
Indicates a change made to a configuration, environment, or parameter value from one state to another.
-
E.
commonUsers
Indicates that two or more entities share at least one user in common, such as overlapping account holders, participants, or audience members.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:02 a.m.