Triple
T28535777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tell Fekheriye region |
E722157
|
entity |
| Predicate | proposedAsLocationOf |
P28981
|
FINISHED |
| Object | Washukanni |
—
|
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: Washukanni | Statement: [Tell Fekheriye region, proposedAsLocationOf, Washukanni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedAsLocationOf Context triple: [Tell Fekheriye region, proposedAsLocationOf, Washukanni]
-
A.
locationProposedFrom
Indicates a proposed or suggested origin location from which something is expected or planned to come.
-
B.
possibleLocation
chosen
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
C.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
D.
plannedLocation
Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- 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_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 3:31 a.m.