Triple
T23417837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alesia |
E560562
|
entity |
| Predicate | modernSiteIdentifiedInCentury |
P152173
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Alesia, modernSiteIdentifiedInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSiteIdentifiedInCentury Context triple: [Alesia, modernSiteIdentifiedInCentury, 19th century]
-
A.
coveredSinceCentury
Indicates that one entity has been covered, coated, or kept under coverage continuously starting from a specified century.
-
B.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
C.
existsSinceCentury
Indicates that an entity has existed or been in effect since a specified century.
-
D.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
E.
observedSinceCentury
Indicates that one entity has been observed or documented as existing or occurring since a specified century.
- F. None of above. chosen
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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a5438ac08190a40a3d6402794699 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:39 p.m.