Triple
T8313711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rubicon River |
E194651
|
entity |
| Predicate | eraOfBoundaryRole |
P81875
|
FINISHED |
| Object | late Roman Republic |
—
|
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: late Roman Republic | Statement: [Rubicon River, eraOfBoundaryRole, late Roman Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfBoundaryRole Context triple: [Rubicon River, eraOfBoundaryRole, late Roman Republic]
-
A.
borderRegionRole
Indicates a role or function that an entity has specifically in relation to a border region or border area.
-
B.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
C.
eraOfCurrentRole
Indicates the historical or temporal era during which the entity’s current role or position is held.
-
D.
stateBorderLengthRole
Indicates that an entity plays a specific role in defining, measuring, or characterizing the length of a state’s border.
-
E.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f52c5cc8190b5a95ee0aa4ddda5 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 5:55 p.m.