Triple
T9803258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oil Crescent region |
E237891
|
entity |
| Predicate | hasBeenSiteOf |
P7849
|
FINISHED |
| Object | armed conflict |
—
|
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: armed conflict | Statement: [Oil Crescent region, hasBeenSiteOf, armed conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenSiteOf Context triple: [Oil Crescent region, hasBeenSiteOf, armed conflict]
-
A.
believedToBeSiteOf
Indicates that something is thought or assumed, though not definitively proven, to be the location where a particular event, structure, or phenomenon occurred or existed.
-
B.
isSiteOf
chosen
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
C.
bestKnownAsSiteOf
Indicates that a place is most widely recognized or famous for being the location where a particular event, activity, or feature occurs or is found.
-
D.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
E.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab78832481909b184b21a8a46e50 |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.