Triple
T7599149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolution (Blackpool Pleasure Beach) |
E179936
|
entity |
| Predicate | hasRcdbNumber |
P78084
|
FINISHED |
| Object | 794 |
—
|
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: 794 | Statement: [Revolution (Blackpool Pleasure Beach), hasRcdbNumber, 794]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRcdbNumber Context triple: [Revolution (Blackpool Pleasure Beach), hasRcdbNumber, 794]
-
A.
hasChamberNumber
Indicates that an entity is associated with a specific chamber identified by a particular number.
-
B.
cabinetNumberInHistory
Indicates the specific cabinet number assigned to an entity within a historical record or context.
-
C.
catalogueRaisonneNumber
Indicates the identifier assigned to a work in a catalogue raisonné, linking it to its authoritative scholarly listing.
-
D.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
E.
notableReaccession
Indicates a significant or noteworthy instance of something being reacquired, reaccepted, or readmitted after having previously left or been removed.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d7cb288190b40ff5c9a09297d9 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:53 p.m.