Triple
T4585461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaziantep Archaeology Museum |
E101956
|
entity |
| Predicate | regionCoveredByCollection |
P19200
|
FINISHED |
| Object | Gaziantep region |
—
|
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: Gaziantep region | Statement: [Gaziantep Archaeology Museum, regionCoveredByCollection, Gaziantep region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCoveredByCollection Context triple: [Gaziantep Archaeology Museum, regionCoveredByCollection, Gaziantep region]
-
A.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
B.
regionCoverage
chosen
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
C.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
-
D.
hasCollectionAt
Indicates that a collection or gathering of items, data, or resources is located, stored, or maintained at a specific place or context.
-
E.
hasCollectionArea
Indicates that an entity is associated with a specific geographic or spatial area from which items, specimens, or data are collected.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59056bb48190ba1e0b5beda9bdc4 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.