Triple
T12104106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | She Who Holds a Thousand Souls |
E288258
|
entity |
| Predicate | numberInEpithet |
P73066
|
FINISHED |
| Object | thousand |
—
|
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: thousand | Statement: [She Who Holds a Thousand Souls, numberInEpithet, thousand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInEpithet Context triple: [She Who Holds a Thousand Souls, numberInEpithet, thousand]
-
A.
epithetOfMonarchNumber
Indicates that a particular epithet (descriptive title or nickname) is associated with a specific numbered monarch in a royal succession.
-
B.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
C.
numberForPraetor
Indicates that an entity is assigned or associated with a specific numerical designation in the context of a praetor.
-
D.
numberInMyth
chosen
Indicates that a given number appears with some significance or role within a particular myth or mythological narrative.
-
E.
numberForCuruleAedile
Indicates the specific numerical value associated with a curule aedile in the given context (such as count, identifier, or rank).
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.