Triple
T34867110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer on the Bluffs |
E1005042
|
entity |
| Predicate | placesInFocus |
P22088
|
FINISHED |
| Object | Oak Bluffs Black community |
—
|
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: Oak Bluffs Black community | Statement: [Summer on the Bluffs, placesInFocus, Oak Bluffs Black community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placesInFocus Context triple: [Summer on the Bluffs, placesInFocus, Oak Bluffs Black community]
-
A.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
-
B.
places
Indicates that one entity assigns, positions, or puts another entity into a specific location, role, or context.
-
C.
placesInQuestion
Indicates that an entity is located within, or occurs in, the spatial or contextual scope defined by a given question.
-
D.
placesInContext
chosen
Indicates that one entity situates, interprets, or frames another entity within a particular context or surrounding circumstances.
-
E.
promotionPlaces
Indicates that one entity designates or assigns another entity to a higher position, rank, or status within some organizational or hierarchical structure.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4 p.m.