Triple
T35732795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argive polis |
E1032802
|
entity |
| Predicate | majorPeriodOfPower |
P5898
|
FINISHED |
| Object | Archaic 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: Archaic period | Statement: [Argive polis, majorPeriodOfPower, Archaic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorPeriodOfPower Context triple: [Argive polis, majorPeriodOfPower, Archaic period]
-
A.
historicalPower
Indicates that one entity held significant influence, control, or authority over another during a past period.
-
B.
periodOfRule
Indicates the span of time during which an entity exercised authority, control, or governance over something.
-
C.
timePeriodOfDominance
chosen
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
D.
prominentDynasty
Indicates that a dynasty holds significant historical, political, or cultural importance relative to other dynasties.
-
E.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:05 p.m.