Triple
T22406224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usipetes |
E553885
|
entity |
| Predicate | interactionWithRome |
P148035
|
FINISHED |
| Object | diplomatic negotiations with 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: diplomatic negotiations with Caesar | Statement: [Usipetes, interactionWithRome, diplomatic negotiations with Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionWithRome Context triple: [Usipetes, interactionWithRome, diplomatic negotiations with Caesar]
-
A.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
B.
significanceToRome
Indicates that something holds particular importance, influence, or relevance in relation to Rome.
-
C.
laterRelationToRome
Indicates that one entity occurs or exists at a time later than the reference time associated with Rome.
-
D.
hillOfRome
Indicates that one entity is a hill that is located in or associated with the city of Rome.
-
E.
returnToRomeTo
Indicates that an entity goes back or returns to the location Rome.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b835e88190a388e19577df771e |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.