Triple
T29777382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esmeralda (emerald) |
E755418
|
entity |
| Predicate | historicallyMinedBy |
P29776
|
FINISHED |
| Object | ancient Egyptians |
—
|
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: ancient Egyptians | Statement: [Esmeralda (emerald), historicallyMinedBy, ancient Egyptians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyMinedBy Context triple: [Esmeralda (emerald), historicallyMinedBy, ancient Egyptians]
-
A.
miningHistory
chosen
Indicates a historical record or past occurrence of mining-related activities or operations associated with an entity.
-
B.
minedSince
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
-
C.
isMinedIn
Indicates that a resource or material is extracted or obtained from a particular location or site.
-
D.
minedOn
Indicates that a resource or material was extracted from a particular location or source on a specific date or time.
-
E.
historicallyBackedBy
Indicates that something is supported, justified, or validated by historical evidence, records, or precedent.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: April 28, 2026, 8:47 p.m.