Triple
T31803945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deglet Nour |
E811817
|
entity |
| Predicate | hasNotableProducingRegion |
P194938
|
FINISHED |
| Object | Biskra |
—
|
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: Biskra | Statement: [Deglet Nour, hasNotableProducingRegion, Biskra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableProducingRegion Context triple: [Deglet Nour, hasNotableProducingRegion, Biskra]
-
A.
coProductionRegions
Indicates the regions or countries that jointly participated in producing a work (e.g., a film or TV show) as co-producers.
-
B.
isProducedIn
Indicates that something is created, manufactured, or generated within a particular place, context, or process.
-
C.
intendedProductionRegion
Indicates the geographic area or region where something is planned or designated to be produced.
-
D.
hasNotableSettlementRegion
Indicates that an entity has a significant or well-known settlement located within a specified geographic region.
-
E.
majorProducerRegion
chosen
Indicates that a region is a primary or significant producer of a particular product, resource, or commodity.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: April 30, 2026, 11:42 p.m.