Triple
T16744682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theophano |
E406920
|
entity |
| Predicate | marriageToRomanosII |
P46634
|
FINISHED |
| Object | took place during the reign of Constantine VII |
—
|
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: took place during the reign of Constantine VII | Statement: [Theophano, marriageToRomanosII, took place during the reign of Constantine VII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageToRomanosII Context triple: [Theophano, marriageToRomanosII, took place during the reign of Constantine VII]
-
A.
marriedToEmperor
chosen
Indicates that one entity is the spouse of an emperor, signifying a marital relationship to a reigning or titled emperor.
-
B.
marriageFormedBy
Indicates that a marriage relationship was created or brought into existence by a specific event, action, or process.
-
C.
formedByMarriageOf
Indicates that something (typically a family, union, or legal entity) comes into existence as a result of the marriage between two entities.
-
D.
endTime (marriage to Nero)
Indicates the point in time at which the marriage to Nero concluded or was terminated.
-
E.
startTime (marriage to Nero)
Indicates the point in time when the marriage to Nero began.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa210ef88190be74bd60d7144953 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.