Triple
T20237122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Octavius Caesar |
E498178
|
entity |
| Predicate | relationshipToJuliusCaesarInPlays |
P38921
|
FINISHED |
| Object | adopted heir |
—
|
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: adopted heir | Statement: [Octavius Caesar, relationshipToJuliusCaesarInPlays, adopted heir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToJuliusCaesarInPlays Context triple: [Octavius Caesar, relationshipToJuliusCaesarInPlays, adopted heir]
-
A.
relationshipToOctavian
Indicates the specific familial, political, or social relationship that one entity has to Octavian.
-
B.
characterActorRelationship
Indicates a relationship where an actor portrays or is associated with a specific character in a work.
-
C.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
D.
roleInFamousPlay
Indicates that an entity portrays or has portrayed a specific character in a well-known theatrical play.
-
E.
famousPlayInvolvedIn
Indicates that a famous play is involved in, or associated with, a particular event, production, or context.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716b4c148190bf663b8a747fbfa5 |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.