Triple
T28908662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syphax – Numidia |
E733155
|
entity |
| Predicate | initialAllegiance |
P145795
|
FINISHED |
| Object | Roman Republic |
—
|
NE NERFINISHED |
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: Roman Republic | Statement: [Syphax – Numidia, initialAllegiance, Roman Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialAllegiance Context triple: [Syphax – Numidia, initialAllegiance, Roman Republic]
-
A.
initiallyAlliedWith
chosen
Indicates that two entities start out in a state of alliance or cooperation at the beginning of a specified period or scenario.
-
B.
commandedUnitAllegiance
Indicates that a military or organizational unit was under the command of, and owed allegiance to, a particular leader or authority.
-
C.
stateAllegiance
Indicates that one entity formally declares loyalty or support to another entity, such as a person, group, or state.
-
D.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
-
E.
opponentForceAllegiance
Indicates that one force, group, or individual is aligned with or belongs to an opposing or enemy side in a conflict or competition.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 8:09 a.m.