Triple
T4674494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spandau Prison |
E103644
|
entity |
| Predicate | repurposedAs |
P47023
|
FINISHED |
| Object | Allied war criminals prison |
—
|
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: Allied war criminals prison | Statement: [Spandau Prison, repurposedAs, Allied war criminals prison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repurposedAs Context triple: [Spandau Prison, repurposedAs, Allied war criminals prison]
-
A.
laterRepurposedFor
chosen
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
B.
isAlsoUsedAs
Indicates that something serves an additional function or role beyond its primary one.
-
C.
formerlyUsedBy
Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
-
D.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
-
E.
eraUsedIn
Indicates that something (such as a method, standard, or practice) was in active use during a specified historical or temporal era.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.