Triple
T23417791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gergovia |
E560561
|
entity |
| Predicate | modernSiteType |
P15047
|
FINISHED |
| Object | archaeological park |
—
|
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: archaeological park | Statement: [Gergovia, modernSiteType, archaeological park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSiteType Context triple: [Gergovia, modernSiteType, archaeological park]
-
A.
modernSiteCorrespondsTo
Indicates that a present-day site occupies, aligns with, or directly relates to the location or extent of another (typically historical or earlier) site.
-
B.
nearModernSite
Indicates that one entity is located in close physical proximity to a site or location from the modern era.
-
C.
traditionalSite
Indicates that a site is recognized or used according to long-established customs, practices, or cultural traditions.
-
D.
typeOfSite
chosen
Indicates the specific category or kind of site that an entity is classified as.
-
E.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a516d158819081e9710b4e372a21 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.