Triple
T31965803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Brunwald |
E816170
|
entity |
| Predicate | guardedByInStory |
P82919
|
FINISHED |
| Object | Nazi soldiers |
—
|
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: Nazi soldiers | Statement: [Castle Brunwald, guardedByInStory, Nazi soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedByInStory Context triple: [Castle Brunwald, guardedByInStory, Nazi soldiers]
-
A.
guardedByInFiction
chosen
Indicates that one fictional entity is protected or watched over by another within a narrative context.
-
B.
controlledByInStory
Indicates that, within the context of a specific story or narrative, one entity exercises control or authority over another.
-
C.
guardedPassage
Indicates that access through a passage is controlled or protected by a guard or security presence.
-
D.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
E.
associatedWithPersonInStory
Indicates that one entity has a connection or involvement with a specific person within the context of a story.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:09 a.m.