Triple
T34000339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tierkidi refugee camp |
E871797
|
entity |
| Predicate | sanitationSystem |
P89306
|
FINISHED |
| Object | latrines |
—
|
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: latrines | Statement: [Tierkidi refugee camp, sanitationSystem, latrines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanitationSystem Context triple: [Tierkidi refugee camp, sanitationSystem, latrines]
-
A.
sanitationInfrastructure
chosen
Indicates the presence, quality, or extent of facilities and systems designed to safely manage human waste and maintain hygienic environmental conditions.
-
B.
hasAblutionFacilities
Indicates that an entity provides or is equipped with facilities for performing ablution or ritual washing.
-
C.
drainageSystemIncludes
Indicates that a particular drainage system contains or encompasses a specified component, segment, or sub-system as part of its overall structure.
-
D.
hasCleaningFacility
Indicates that an entity provides or is equipped with a facility or service for cleaning.
-
E.
wasteManagementFacility
Indicates a facility where waste materials are collected, processed, treated, or disposed of as part of a waste management system.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.