Triple
T29662017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tullia Ciceronis |
E750435
|
entity |
| Predicate | marriedFuriusCrassipesAround |
P141854
|
FINISHED |
| Object | 63 BC |
—
|
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: 63 BC | Statement: [Tullia Ciceronis, marriedFuriusCrassipesAround, 63 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedFuriusCrassipesAround Context triple: [Tullia Ciceronis, marriedFuriusCrassipesAround, 63 BC]
-
A.
marriedToEmperor
Indicates that one entity is the spouse of an emperor, signifying a marital relationship to a reigning or titled emperor.
-
B.
relationshipToCrassus
chosen
Indicates a relationship or association that one entity has with Crassus, specifying how it is connected or related to him.
-
C.
marriageEndToPompey
Indicates that a marriage concluded or was terminated in relation to Pompey (e.g., by divorce, annulment, or death).
-
D.
marriageToConstantiusGallus
Indicates a marital relationship in which one entity is married to Constantius Gallus.
-
E.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 28, 2026, 6:59 p.m.