Triple
T36492885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarrant Hinton |
E899097
|
entity |
| Predicate | GreatDorsetSteamFairAttractions |
P187000
|
FINISHED |
| Object | steam engines |
—
|
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: steam engines | Statement: [Tarrant Hinton, GreatDorsetSteamFairAttractions, steam engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GreatDorsetSteamFairAttractions Context triple: [Tarrant Hinton, GreatDorsetSteamFairAttractions, steam engines]
-
A.
GreatDorsetSteamFairType
Indicates that there is a relationship involving the type or category classification associated with the Great Dorset Steam Fair.
-
B.
GreatDorsetSteamFairSeason
Indicates that something occurs during, is associated with, or pertains to the seasonal period of the Great Dorset Steam Fair.
-
C.
GreatDorsetSteamFairFounded
Indicates that an entity is the person or organization that founded the Great Dorset Steam Fair.
-
D.
partOfAttractionType
Indicates that one attraction type is a component or subset of a broader, more general attraction type.
-
E.
themeParkAttraction
Indicates that something is an attraction or ride located within a theme park.
- F. None of above. chosen
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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.