Triple
T33112735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruinen |
E847372
|
entity |
| Predicate | usedAsDefenseFor |
P119087
|
FINISHED |
| Object | Rivendell |
—
|
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: Rivendell | Statement: [Bruinen, usedAsDefenseFor, Rivendell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsDefenseFor Context triple: [Bruinen, usedAsDefenseFor, Rivendell]
-
A.
defensiveUse
chosen
Indicates that an entity uses something primarily for protection or defense against threats or attacks.
-
B.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
C.
typeOfDefense
Indicates the specific kind or category of defense employed or possessed in a given context.
-
D.
alsoDefendedIn
Indicates that the same entity or case was defended in an additional context, such as another court, proceeding, or jurisdiction.
-
E.
defenceUsed
Indicates that a particular defensive measure, tactic, or argument was employed in response to a threat, attack, or accusation.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 1, 2026, 1:27 a.m.