Triple
T35879064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loudoun Castle |
E1037456
|
entity |
| Predicate | themeParkOpeningDate |
P44881
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Loudoun Castle, themeParkOpeningDate, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeParkOpeningDate Context triple: [Loudoun Castle, themeParkOpeningDate, 1995]
-
A.
originalAttractionOpeningDate
Indicates the date on which the attraction first opened to the public in its original form or location.
-
B.
themeParkConnection
Indicates a relationship where two or more entities are connected through a theme park, such as by location, operation, partnership, or shared attractions.
-
C.
themeParkPresence
Indicates that an entity is present at, located in, or associated with a theme park in the context of a given event or situation.
-
D.
openingDateAsPark
chosen
Indicates the date on which a place or area was first officially opened and began operating as a park.
-
E.
themeParkComplex
Indicates a relationship where one entity is a theme park complex that encompasses or is composed of the other entity or entities.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.