Triple
T7420362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Desert of Egypt |
E171229
|
entity |
| Predicate | modernEconomicUse |
P3592
|
FINISHED |
| Object | mineral extraction |
—
|
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: mineral extraction | Statement: [Eastern Desert of Egypt, modernEconomicUse, mineral extraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernEconomicUse Context triple: [Eastern Desert of Egypt, modernEconomicUse, mineral extraction]
-
A.
modernUse
Indicates how something is currently used or applied in modern times.
-
B.
economicUse
chosen
Indicates that one entity utilizes another for economic purposes, such as production, trade, revenue generation, or cost-saving activities.
-
C.
hasMainEconomicUse
Indicates that something serves as the primary or principal economic function, purpose, or use of another entity.
-
D.
modernIndustry
Indicates that an entity operates within or is characteristic of contemporary, technologically advanced industrial practices and sectors.
-
E.
modernizationPurpose
Indicates that an action or change is carried out with the aim of updating, improving, or bringing something in line with contemporary standards, practices, or technologies.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ea61248190886e8e55b42ba5f1 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.