Triple
T6079674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gross-Rosen concentration camp |
E135489
|
entity |
| Predicate | todayUsedAs |
P58057
|
FINISHED |
| Object | memorial site |
—
|
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: memorial site | Statement: [Gross-Rosen concentration camp, todayUsedAs, memorial site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: todayUsedAs Context triple: [Gross-Rosen concentration camp, todayUsedAs, memorial site]
-
A.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
B.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
C.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
usageToday
chosen
Indicates the current or most recent use or application of something on the present day.
-
E.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0577209b88190afe5b1365cf6436d |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.