Triple
T6393847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peisistratos |
E143892
|
entity |
| Predicate | regainedPowerDate |
P3245
|
FINISHED |
| Object | c. 546 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. 546 BCE | Statement: [Peisistratos, regainedPowerDate, c. 546 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regainedPowerDate Context triple: [Peisistratos, regainedPowerDate, c. 546 BCE]
-
A.
regainedPowerIn
Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
-
B.
regainedPowerAgainIn
chosen
Indicates that an entity, having previously lost power, has once more returned to a position of power or control within a specified context or location.
-
C.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
-
D.
retrocessionDate
Indicates the date on which rights, obligations, or control previously transferred are formally returned or reassigned back to the original party or another designated party.
-
E.
inPowerSince
Indicates the point in time from which an entity has continuously held a position of authority or power.
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06881313481908e9082ffe57f29b6 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:34 p.m.