Triple
T36629180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Périgord |
E904261
|
entity |
| Predicate | notablePrehistoricSite |
P18735
|
FINISHED |
| Object | Lascaux |
E379197
|
NE 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: Lascaux | Statement: [Périgord, notablePrehistoricSite, Lascaux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePrehistoricSite Context triple: [Périgord, notablePrehistoricSite, Lascaux]
-
A.
notableArchaeologicalSite
chosen
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
-
B.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
C.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
D.
cultSite
Indicates a location that is or was used for religious or ritual worship activities.
-
E.
notableDiscoveryAtSite
Indicates that an entity is recognized for having made an important discovery at a particular site.
- F. None of above.
Provenance (4 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a20c18c1c8190b178ffc1541d187c |
completed | June 23, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.