Triple
T8313703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rubicon River |
E194651
|
entity |
| Predicate | crossingDate |
P81874
|
FINISHED |
| Object | 49 BCE |
—
|
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: 49 BCE | Statement: [Rubicon River, crossingDate, 49 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossingDate Context triple: [Rubicon River, crossingDate, 49 BCE]
-
A.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
B.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
C.
crossingOpened
Indicates that a crossing (such as a road, rail, or pedestrian crossing) has been opened or made available for passage.
-
D.
crossesBetween
Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
-
E.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
- 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.