Triple
T16801532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdera |
E408367
|
entity |
| Predicate | foundationCenturyBC |
P54941
|
FINISHED |
| Object | 7th century BC |
—
|
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: 7th century BC | Statement: [Abdera, foundationCenturyBC, 7th century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundationCenturyBC Context triple: [Abdera, foundationCenturyBC, 7th century BC]
-
A.
constructedInCenturyBCE
Indicates that something was built or created during a specified century before the Common Era (BCE).
-
B.
eraChronology
Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
-
C.
approximateEndCenturyBCE_CE
Indicates that an event or entity is estimated to have ended in a particular century, which may be expressed in either BCE or CE.
-
D.
baseAfter1stCentury
Indicates that something is based in a time period occurring after the 1st century.
-
E.
colonizationCenturyBC
chosen
Indicates the century before the Common Era in which a colonization event or process took place.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2c826808190aa0a5bfcde2e49a8 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.