Triple
T31835430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Publius Vatinius |
E812657
|
entity |
| Predicate | lex VatiniaGranted |
P172645
|
FINISHED |
| Object | proconsular command in Gaul to Julius Caesar |
—
|
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: proconsular command in Gaul to Julius Caesar | Statement: [Publius Vatinius, lex VatiniaGranted, proconsular command in Gaul to Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lex VatiniaGranted Context triple: [Publius Vatinius, lex VatiniaGranted, proconsular command in Gaul to Julius Caesar]
-
A.
vadi
Indicates that one entity is speaking, arguing, or verbally expressing something to another entity.
-
B.
vitDans
Indicates that one entity lives or resides in the location represented by another entity.
-
C.
victor
Indicates that one entity is the winner or has prevailed over another in a contest, conflict, or competition.
-
D.
hasVow
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
-
E.
VarunaIs
Indicates that an entity is identified as or associated with Varuna.
- F. None of above. chosen
Provenance (4 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b034bc74819091250f91ba5174c0 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:48 p.m.