Triple
T2345150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton |
E45112
|
entity |
| Predicate | developmentAsResortBegan |
P10779
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Brighton, developmentAsResortBegan, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentAsResortBegan Context triple: [Brighton, developmentAsResortBegan, 18th century]
-
A.
openedAsResort
Indicates that something began operating or was first established in the capacity of a resort.
-
B.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
C.
resortNameAdopted
Indicates that a particular name has been officially adopted or designated for use as the name of a resort.
-
D.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
E.
developmentBegan
chosen
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.