Triple
T13432899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potidaea |
E320155
|
entity |
| Predicate | refoundationDate |
P9526
|
FINISHED |
| Object | 316 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: 316 BCE | Statement: [Potidaea, refoundationDate, 316 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refoundationDate Context triple: [Potidaea, refoundationDate, 316 BCE]
-
A.
reFoundationDate
chosen
Indicates the date on which an entity was re-established or founded again after a previous foundation.
-
B.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
C.
refoundedBy
Indicates that an entity was re-established or reconstituted by another entity after a period of inactivity, dissolution, or significant change.
-
D.
claimedFoundationDate
Indicates the date that an entity asserts or reports as its founding date, regardless of historical accuracy.
-
E.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaed41a5481908800033303224adb |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.