Triple
T30927689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabini |
E787902
|
entity |
| Predicate | eventualRelationToRome |
P60436
|
FINISHED |
| Object | incorporated into Roman state |
—
|
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: incorporated into Roman state | Statement: [Sabini, eventualRelationToRome, incorporated into Roman state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventualRelationToRome Context triple: [Sabini, eventualRelationToRome, incorporated into Roman state]
-
A.
laterRelationToRome
chosen
Indicates that one entity occurs or exists at a time later than the reference time associated with Rome.
-
B.
initialRelationToRome
Indicates the nature of an entity’s earliest recorded or original relationship, status, or connection to Rome.
-
C.
transportedToRomeIn
Indicates that something or someone was transported or moved to Rome at a particular time or by a particular means.
-
D.
interactionWithRome
Indicates a relationship in which an entity engages in some form of contact, exchange, or involvement with Rome.
-
E.
returnToRomeTo
Indicates that an entity goes back or returns to the location Rome.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 8:51 p.m.