Triple
T31567736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mediana archaeological site |
E805463
|
entity |
| Predicate | timeOfDiscovery |
P3836
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Mediana archaeological site, timeOfDiscovery, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDiscovery Context triple: [Mediana archaeological site, timeOfDiscovery, 20th century]
-
A.
discoveryDate
chosen
Indicates the date on which something was first discovered or identified.
-
B.
ageWhenDiscovered
Indicates the age of an entity at the time it was first discovered.
-
C.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
D.
eraOfDiscovery
Indicates a relationship where something belongs to, occurs in, or is characteristic of a specific era of discovery or exploration.
-
E.
causeOfDiscovery
Indicates that one entity is the reason or factor that led to the discovery of another entity.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 30, 2026, 10:18 p.m.