Triple
T38633939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maues |
E937529
|
entity |
| Predicate | probableReignStart |
P1506
|
FINISHED |
| Object | circa 85 BCE |
—
|
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: circa 85 BCE | Statement: [Maues, probableReignStart, circa 85 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: probableReignStart Context triple: [Maues, probableReignStart, circa 85 BCE]
-
A.
possibleReignPeriod
Indicates a time interval during which an entity could have held ruling authority, without asserting that it definitively did so.
-
B.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
C.
heirPresumptivePeriodStart
Indicates the point in time when an individual first becomes the heir presumptive to a title, position, or estate.
-
D.
reignStartBefore
Indicates that the start of one entity’s reign occurs earlier in time than the start of another entity’s reign.
-
E.
reignApproximateDates
Indicates that the time period associated with a ruler’s reign is known only approximately, rather than with precise start and end dates.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.