Triple
T35659763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gulls |
E1030394
|
entity |
| Predicate | associatedWithSeasideTown |
P47434
|
FINISHED |
| Object | Torquay |
E80572
|
NE 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: Torquay | Statement: [The Gulls, associatedWithSeasideTown, Torquay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSeasideTown Context triple: [The Gulls, associatedWithSeasideTown, Torquay]
-
A.
associatedWithTownType
Indicates that an entity has a relationship or linkage to a particular category or classification of town (e.g., village, city, suburb).
-
B.
associatedWithSea
chosen
Indicates a relationship in which something has a connection, relevance, or linkage to the sea or marine environment.
-
C.
isSeasideCounterpartOf
Indicates that one entity serves as the seaside equivalent or corresponding version of another entity.
-
D.
associatedWithCountySeat
Indicates that an entity has a relationship or connection to a county’s administrative center or county seat.
-
E.
associatedWithSubdivision
Indicates that one entity has a connection or linkage to a specific administrative or organizational subdivision.
- F. None of above.
Provenance (4 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38dde852ac8190a413515e51f8152a |
completed | June 22, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.