Triple
T28535791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tell Fekheriye region |
E722157
|
entity |
| Predicate | inBroadRegion |
P128393
|
FINISHED |
| Object | Upper Mesopotamia |
—
|
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: Upper Mesopotamia | Statement: [Tell Fekheriye region, inBroadRegion, Upper Mesopotamia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inBroadRegion Context triple: [Tell Fekheriye region, inBroadRegion, Upper Mesopotamia]
-
A.
hasBroadRegion
chosen
Indicates that an entity is associated with, located in, or applicable to a relatively large or general geographic or conceptual region.
-
B.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
C.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
- 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_69f64fda797081909e259eb25d51e206 |
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.