Triple
T2648325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaumaris Castle |
E53834
|
entity |
| Predicate | hasDefensiveElement |
P8412
|
FINISHED |
| Object | arrow loops |
—
|
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: arrow loops | Statement: [Beaumaris Castle, hasDefensiveElement, arrow loops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefensiveElement Context triple: [Beaumaris Castle, hasDefensiveElement, arrow loops]
-
A.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
B.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
-
C.
defensiveStructure
chosen
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
D.
defenceHandledBy
Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
-
E.
isDefensiveStock
Indicates that a stock tends to maintain its value and perform relatively steadily during market downturns or economic uncertainty.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91b4b3c81908571e85a1621dfc5 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.