Triple
T35849466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papremis |
E1036308
|
entity |
| Predicate | approximateDateOfRevolt |
P4699
|
FINISHED |
| Object | c. 460–454 BCE |
—
|
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: c. 460–454 BCE | Statement: [Papremis, approximateDateOfRevolt, c. 460–454 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfRevolt Context triple: [Papremis, approximateDateOfRevolt, c. 460–454 BCE]
-
A.
uprisingDate
chosen
Indicates the date on which an uprising or rebellion occurred or began.
-
B.
rebellionOccurredAfter
Indicates that the rebellion took place later in time than the referenced event or situation.
-
C.
revoltOccurredDuring
Indicates that a revolt took place within the temporal span of a specified event or period.
-
D.
uprisingPlannedAt
Indicates that a planned uprising or rebellion is scheduled to occur at a specific location or time.
-
E.
firstMajorUprisingEndDate
Indicates the date on which the first major uprising associated with the subject came to an end.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 3, 2026, 4:06 p.m.