Triple
T35319116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeus Lepsynos |
E1019987
|
entity |
| Predicate | hasPrimaryPeriod |
P28924
|
FINISHED |
| Object | Hellenistic period |
—
|
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: Hellenistic period | Statement: [Zeus Lepsynos, hasPrimaryPeriod, Hellenistic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryPeriod Context triple: [Zeus Lepsynos, hasPrimaryPeriod, Hellenistic period]
-
A.
hasMainPeriod
chosen
Indicates that something is associated with or characterized by a primary or most significant time period.
-
B.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
C.
hasSecondaryPeriod
Indicates that an entity is associated with an additional, subordinate, or second time period beyond its primary period.
-
D.
hasPrimaryDate
Indicates that an entity is associated with its main or most significant date (such as a primary event, creation, or reference date) among potentially multiple dates.
-
E.
hasPrimaryFocusPeriod
Indicates that something is chiefly concerned with, or centered on, a particular period of 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.