Triple
T28688004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Antonius |
E729189
|
entity |
| Predicate | allyInConflict |
P165217
|
FINISHED |
| Object | Fulvia |
E211412
|
NE 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: Fulvia | Statement: [Lucius Antonius, allyInConflict, Fulvia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allyInConflict Context triple: [Lucius Antonius, allyInConflict, Fulvia]
-
A.
formedInConflict
Indicates that an entity came into existence as a direct result of, or during the course of, a specific conflict or war.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
D.
ongoingConflict
Indicates a sustained, unresolved state of opposition or hostilities continuing between the involved entities.
-
E.
militaryConflictIn
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
- F. None of above. chosen
Provenance (5 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1cc3b0436481909b6a4c9e4dfc9cfa |
completed | May 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 5:34 a.m.