Triple
T35762220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camber Castle |
E1033906
|
entity |
| Predicate | garrisonDisbanded |
P66716
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Camber Castle, garrisonDisbanded, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonDisbanded Context triple: [Camber Castle, garrisonDisbanded, 17th century]
-
A.
garrisonDestroyed
Indicates that a military garrison has been eliminated or rendered nonfunctional, typically through attack or destruction.
-
B.
garrisonAfterEvacuation
Indicates that a military force is stationed in a location following a prior evacuation of that location.
-
C.
disbandedDueTo
Indicates that an organization, group, or entity ceased to exist specifically as a result of a particular cause, event, or condition.
-
D.
disbandedDuring
chosen
Indicates that an entity ceased to exist or was formally dissolved at some point within the duration of a specified event or time period.
-
E.
garrisonAfterWar
Indicates that a military force is stationed in or occupies a location following the end of a war or major conflict.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1c562848190ba1fe4f9cb7efa87 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.