Triple
T25013799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Fork |
E626070
|
entity |
| Predicate | majorHamletsInclude |
P12354
|
FINISHED |
| Object | Bridgehampton |
—
|
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: Bridgehampton | Statement: [South Fork, majorHamletsInclude, Bridgehampton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorHamletsInclude Context triple: [South Fork, majorHamletsInclude, Bridgehampton]
-
A.
hasHamlet
chosen
Indicates that an entity possesses, contains, or is associated with a hamlet (a small settlement).
-
B.
hasShakespeareTheme
Indicates that something embodies, features, or is characterized by a theme originating from or strongly associated with Shakespeare’s works.
-
C.
famousPlay
Indicates that the subject is a well-known or widely recognized theatrical play.
-
D.
famousPlayInvolvedIn
Indicates that a famous play is involved in, or associated with, a particular event, production, or context.
-
E.
mostFamousPlay
Indicates that the related entity is the play for which a person is best or most widely known.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 6:06 a.m.