Triple
T28535425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washukanni |
E722149
|
entity |
| Predicate | hypothesizedLocationNear |
P61270
|
FINISHED |
| Object | Tell Fekheriye |
—
|
NE NERFINISHED |
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: Tell Fekheriye | Statement: [Washukanni, hypothesizedLocationNear, Tell Fekheriye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hypothesizedLocationNear Context triple: [Washukanni, hypothesizedLocationNear, Tell Fekheriye]
-
A.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
B.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
C.
partlyLocatedNear
Indicates that one entity is situated near another, but only a portion or subset of it lies within that nearby area.
-
D.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
-
E.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fd960b08190844c66ad659ebbc6 |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:31 a.m.