Triple
T34406849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korem |
E883137
|
entity |
| Predicate | hasReliefCamp |
P30108
|
FINISHED |
| Object | Korem famine relief camp (1980s) |
—
|
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: Korem famine relief camp (1980s) | Statement: [Korem, hasReliefCamp, Korem famine relief camp (1980s)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReliefCamp Context triple: [Korem, hasReliefCamp, Korem famine relief camp (1980s)]
-
A.
hasRelief
Indicates that one entity features or exhibits a raised or sculpted surface design (relief) in relation to another entity or context.
-
B.
hasReliefOf
Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
-
C.
hasRefugeeCamp
chosen
Indicates that a location or entity hosts, contains, or is the site of a refugee camp.
-
D.
hasReliefsFrom
Indicates that one entity experiences a reduction or alleviation of symptoms, problems, or burdens as a result of another entity.
-
E.
hasReliefFeature
Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:59 a.m.