Triple
T9911880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimue |
E185162
|
entity |
| Predicate | imprisonmentMethod |
P22043
|
FINISHED |
| Object | magical cave (in some versions) |
—
|
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: magical cave (in some versions) | Statement: [Nimue, imprisonmentMethod, magical cave (in some versions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imprisonmentMethod Context triple: [Nimue, imprisonmentMethod, magical cave (in some versions)]
-
A.
usedForImprisoning
chosen
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
-
B.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
C.
imprisonedWith
Indicates that two entities are confined or held in prison together at the same time and place.
-
D.
imprisonedFor
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
-
E.
imprisonmentContext
Indicates that one entity is held in confinement or custody by another entity or authority within a specific legal, temporal, or situational 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb5391b8081908094b88cdde4b55a |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.