Triple
T37805758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royalist defense of the Thames Valley |
E942494
|
entity |
| Predicate | involvedStronghold |
P197870
|
FINISHED |
| Object | Oxford |
—
|
NE NERFINISHED |
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: Oxford | Statement: [Royalist defense of the Thames Valley, involvedStronghold, Oxford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedStronghold Context triple: [Royalist defense of the Thames Valley, involvedStronghold, Oxford]
-
A.
strongholdOf
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
B.
strongholdRecapturedBy
Indicates that control of a previously held stronghold has been regained by a specified entity after it was lost or captured.
-
C.
strongholdRecapturedWithAidOf
Indicates that a stronghold was retaken by one party with assistance or support from another party.
-
D.
currentStronghold
Indicates that an entity currently serves as the primary base, fortress, or central stronghold for another entity.
-
E.
primaryStronghold
Indicates that one location serves as the main base, fortress, or central stronghold for an entity compared to its other sites.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
| PDg | Predicate description generation | batch_69feb3419158819082f4666077535ca9 |
completed | May 9, 2026, 4:08 a.m. |
Created at: May 3, 2026, 4:19 p.m.