Triple
T30168005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan kings |
E766846
|
entity |
| Predicate | dynasties |
P1547
|
FINISHED |
| Object | Agiad dynasty |
—
|
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: Agiad dynasty | Statement: [Spartan kings, dynasties, Agiad dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasties Context triple: [Spartan kings, dynasties, Agiad dynasty]
-
A.
dynasty
chosen
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
B.
traditionalDynasty
Indicates a relationship where a dynasty is recognized as traditional, typically long-established and rooted in customary or historical authority.
-
C.
dynastyDescribedAs
Indicates that a dynasty is characterized or labeled using a particular description, epithet, or qualitative phrase.
-
D.
dynasticScope
Indicates the range or extent of influence, authority, or relevance associated with a particular dynasty or dynastic period.
-
E.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 7:23 p.m.