Triple
T11266058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle & Key Distillery |
E266687
|
entity |
| Predicate | reopenedAsCastleAndKeyIn |
P98828
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Castle & Key Distillery, reopenedAsCastleAndKeyIn, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsCastleAndKeyIn Context triple: [Castle & Key Distillery, reopenedAsCastleAndKeyIn, 2018]
-
A.
castleRestoredBy
Indicates that a castle has been repaired, renovated, or returned to a previous condition through the efforts or actions of a specified agent.
-
B.
hasCastle
Indicates that one entity possesses, controls, or contains a castle.
-
C.
eraOfMainCastle
Indicates the historical period or era during which the main castle associated with an entity was built, used, or most prominent.
-
D.
castlePosition
Indicates the spatial location or placement of a castle relative to a reference point or area.
-
E.
castleStatus
Indicates the current condition or state of a castle, such as whether it is intact, damaged, occupied, abandoned, or under construction.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94e5e3c8190a31995d55d20d7ed |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.