Triple
T8239747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ghost |
E192504
|
entity |
| Predicate | relationshipToClaudius |
P79058
|
FINISHED |
| Object | brother |
—
|
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: brother | Statement: [The Ghost, relationshipToClaudius, brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToClaudius Context triple: [The Ghost, relationshipToClaudius, brother]
-
A.
associatedWithEmperor
Indicates a relationship in which an entity has a connection, link, or affiliation with an emperor, such as through service, influence, kinship, or shared authority.
-
B.
familyRelationToEmperor
chosen
Indicates that one entity is related to an emperor by family ties, specifying a kinship or familial connection between them.
-
C.
successorAsEasternAugustus
Indicates that one entity becomes the next holder of the title of Eastern Augustus immediately following another entity in succession.
-
D.
fatherWasEmperorOf
Indicates that the person referred to as the father held the position or title of emperor of the specified entity (such as a state, empire, or territory).
-
E.
predecessorAsEasternAugustus
Indicates that one entity previously held the position of Eastern Roman Emperor immediately before the other 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783cce5c8190bf116704d2923ade |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.