Triple
T20237099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Octavius Caesar |
E498178
|
entity |
| Predicate | roleInJuliusCaesar |
P81380
|
FINISHED |
| Object | supporting character |
—
|
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: supporting character | Statement: [Octavius Caesar, roleInJuliusCaesar, supporting character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInJuliusCaesar Context triple: [Octavius Caesar, roleInJuliusCaesar, supporting character]
-
A.
roleInGallicWars
Indicates the role or involvement an entity had in the events or campaigns of the Gallic Wars.
-
B.
roleInPunicWars
Indicates the specific involvement, function, or position an entity had in the events or campaigns of the Punic Wars.
-
C.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
D.
roleInRomeoAndJuliet
chosen
Indicates the specific character or part that an entity plays in the work "Romeo and Juliet."
-
E.
role in Jugurthine War
Indicates the specific function, position, or involvement an entity had in the events and operations of the Jugurthine War.
- 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_69e6716a5af0819095ea419a4d1f0d1d |
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.