Triple
T26435132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alt Clut |
E664922
|
entity |
| Predicate | fellInSiegeOf |
P103407
|
FINISHED |
| Object | Dumbarton Rock |
—
|
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: Dumbarton Rock | Statement: [Alt Clut, fellInSiegeOf, Dumbarton Rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fellInSiegeOf Context triple: [Alt Clut, fellInSiegeOf, Dumbarton Rock]
-
A.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
-
B.
wasBesiegedBy
chosen
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
C.
siegeRelated
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
-
D.
resultOfSiege
Indicates that one entity is the outcome or consequence produced by a siege conducted against another entity.
-
E.
sieged
Indicates that one entity has surrounded and blockaded another entity or location, typically to cut off supplies and force surrender.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61210575c8190b84b012054b6f26d |
completed | May 2, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:53 p.m.