Triple
T9662090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamhat |
E233612
|
entity |
| Predicate | encounterLocation |
P89472
|
FINISHED |
| Object | watering place in the wilderness |
—
|
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: watering place in the wilderness | Statement: [Shamhat, encounterLocation, watering place in the wilderness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterLocation Context triple: [Shamhat, encounterLocation, watering place in the wilderness]
-
A.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
-
B.
examinationLocation
Indicates the place or setting where an examination or test is conducted.
-
C.
treatmentLocation
Indicates the place or facility where a treatment or medical intervention is administered to an entity.
-
D.
dischargeLocation
Indicates the place or facility where an entity (such as a person, object, or substance) is released, sent, or discharged to after a prior state or process.
-
E.
locationOfFacility
Indicates that a facility is situated at or associated with a specific geographic location.
- F. None of above. chosen
Provenance (4 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:14 p.m.