Triple
T11760091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sullivan & Son |
E279631
|
entity |
| Predicate | primaryLocationWithinSetting |
P14490
|
FINISHED |
| Object | family-owned bar |
—
|
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: family-owned bar | Statement: [Sullivan & Son, primaryLocationWithinSetting, family-owned bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLocationWithinSetting Context triple: [Sullivan & Son, primaryLocationWithinSetting, family-owned bar]
-
A.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
B.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
C.
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.
-
D.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
E.
locationOfControl
Indicates that one entity is the place or context in which another entity exercises authority, management, or control.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a52386708190b744746a2db37495 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.