Triple
T30168008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan kings |
E766846
|
entity |
| Predicate | powerSharingWith |
P2444
|
FINISHED |
| Object | Gerousia |
—
|
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: Gerousia | Statement: [Spartan kings, powerSharingWith, Gerousia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSharingWith Context triple: [Spartan kings, powerSharingWith, Gerousia]
-
A.
sharesPowerWith
chosen
Indicates that two or more entities jointly hold, exercise, or distribute authority or control in a shared manner.
-
B.
sharesCustodyWith
Indicates that two or more parties jointly hold legal responsibility and decision-making authority for the care and upbringing of the same dependent, typically a child.
-
C.
sharesOwnershipWith
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
-
D.
sharesControlWith
Indicates that control, authority, or decision-making power over something is jointly held or exercised between the related entities.
-
E.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
- 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_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 7:23 p.m.