Triple
T35867694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphakteria |
E1037130
|
entity |
| Predicate | eraOfMainHistoricalImportance |
P5250
|
FINISHED |
| Object | Classical Greece |
—
|
NE NERFINISHED |
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: Classical Greece | Statement: [Sphakteria, eraOfMainHistoricalImportance, Classical Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfMainHistoricalImportance Context triple: [Sphakteria, eraOfMainHistoricalImportance, Classical Greece]
-
A.
historicalPeople
Indicates that the related entities are people who lived in or are associated with a past historical period or context.
-
B.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
C.
roleInHumanHistory
Indicates the function, influence, or significance that an entity has had within the course of human history.
-
D.
eraOfSignificance
chosen
Indicates the historical period or timeframe during which an entity was particularly important, influential, or noteworthy.
-
E.
eraOfHistoricalAssociation
Indicates the historical time period during which the association or relationship between the entities 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:06 p.m.