Triple
T8916162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mixed constitution (Sparta) |
E212300
|
entity |
| Predicate | ephorsNumber |
P8195
|
FINISHED |
| Object | 5 ephors |
—
|
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: 5 ephors | Statement: [mixed constitution (Sparta), ephorsNumber, 5 ephors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ephorsNumber Context triple: [mixed constitution (Sparta), ephorsNumber, 5 ephors]
-
A.
imoNumber
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
-
B.
numberInMyth
Indicates that a given number appears with some significance or role within a particular myth or mythological narrative.
-
C.
evaCount
Indicates a relationship where a specific count or number is associated with an evaluation-related event, action, or occurrence.
-
D.
pillarNumber
Indicates the specific numerical identifier assigned to a particular pillar within a set or structure.
-
E.
number
chosen
Indicates that one entity is associated with a specific numerical value or count in relation to another entity 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc660f6a088190b0af829ea809d8ad |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.