Triple
T4214962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rothesay Castle |
E94191
|
entity |
| Predicate | defensiveType |
P8412
|
FINISHED |
| Object | stone castle |
—
|
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: stone castle | Statement: [Rothesay Castle, defensiveType, stone castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveType Context triple: [Rothesay Castle, defensiveType, stone castle]
-
A.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
B.
defensiveStructure
chosen
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
C.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
D.
defensiveTactics
Indicates the use or implementation of strategies, maneuvers, or methods intended to protect, guard, or defend against threats or attacks.
-
E.
typeOfDefense
Indicates the specific kind or category of defense employed or possessed in a given context.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.