Triple
T457441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stalags |
E7263
|
entity |
| Predicate | notoriousFor |
P22
|
FINISHED |
| Object | harsh conditions |
—
|
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: harsh conditions | Statement: [Stalags, notoriousFor, harsh conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notoriousFor Context triple: [Stalags, notoriousFor, harsh conditions]
-
A.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
notableAdversary
Indicates that one entity is recognized as a significant or prominent opponent or rival of another entity.
-
C.
notableFact
Indicates that there exists a particularly significant or noteworthy fact or piece of information associated with the subject.
-
D.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa1616481909399f92551a0c9e3 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.