Triple
T35879066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loudoun Castle |
E1037456
|
entity |
| Predicate | themeParkStatus |
P184910
|
FINISHED |
| Object | closed |
—
|
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: closed | Statement: [Loudoun Castle, themeParkStatus, closed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeParkStatus Context triple: [Loudoun Castle, themeParkStatus, closed]
-
A.
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.
-
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.
themeParkClosingDate
Indicates the date on which a theme park ceases operations or closes, either temporarily or permanently.
-
D.
themeParkComplex
Indicates a relationship where one entity is a theme park complex that encompasses or is composed of the other entity or entities.
-
E.
themeParkAccess
Indicates that an entity has permission or eligibility to enter or use the facilities and attractions of 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.