Triple
T28833460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asira ash-Shamaliya |
E728113
|
entity |
| Predicate | locatedInLevant |
P200940
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Asira ash-Shamaliya, locatedInLevant, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLevant Context triple: [Asira ash-Shamaliya, locatedInLevant, yes]
-
A.
locatedInModernAdministrativeRegion
Indicates that an entity is geographically situated within the boundaries of a current, officially recognized administrative region.
-
B.
laterRegionInAntiquity
Indicates that one region existed or was defined later in antiquity than another region, reflecting a temporal succession between them.
-
C.
importanceInLevant
Indicates the degree to which something holds significance, influence, or prominence within the context of the Levant region.
-
D.
regionOnWestBank
Indicates that one region is located on the western bank of another geographic feature, such as a river or body of water.
-
E.
locatedInNorthernUpperEgypt
Indicates that the subject is geographically situated in the northern part of Upper Egypt.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
| PDg | Predicate description generation | batch_69ffbb1b3b888190ba329ad321fc3f3d |
completed | May 9, 2026, 10:54 p.m. |
Created at: April 28, 2026, 6:38 a.m.