Triple
T8955187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gazans |
E213453
|
entity |
| Predicate | notableCampType |
P19521
|
FINISHED |
| Object | refugee camps administered by UNRWA |
—
|
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: refugee camps administered by UNRWA | Statement: [Gazans, notableCampType, refugee camps administered by UNRWA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCampType Context triple: [Gazans, notableCampType, refugee camps administered by UNRWA]
-
A.
notableCamp
Indicates that an entity is a camp that is notable or significant in some recognized way (e.g., historically, culturally, or by prominence).
-
B.
notableResort
Indicates that a location functions as a resort that is recognized for its significance, prominence, or special reputation.
-
C.
notableDestinationType
Indicates the general category or type of destination for which something is considered notable.
-
D.
campCategory
chosen
Indicates the classification or type of camp to which an entity belongs (e.g., by purpose, style, or characteristics).
-
E.
hasCampingOption
Indicates that an entity offers or includes the possibility to camp (e.g., designated camping facilities or areas).
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6726cec48190a900ae52b1522adb |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.