Triple
T31077707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicus Caprarius |
E792010
|
entity |
| Predicate | associatedWithAqueduct |
P207343
|
FINISHED |
| Object | Aqua Virgo |
E539880
|
NE 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: Aqua Virgo | Statement: [Vicus Caprarius, associatedWithAqueduct, Aqua Virgo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithAqueduct Context triple: [Vicus Caprarius, associatedWithAqueduct, Aqua Virgo]
-
A.
associatedWithWaterways
Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
-
B.
associatedWithSea
Indicates a relationship in which something has a connection, relevance, or linkage to the sea or marine environment.
-
C.
drainageAssociatedWith
Indicates that one entity has a drainage relationship or connection with another, such as sharing, affecting, or being linked through water or fluid drainage.
-
D.
associatedWithWaterfront
Indicates a relationship in which something is located on, adjacent to, or otherwise directly connected with a waterfront area.
-
E.
associatedWithGround
Indicates that an entity has a defined connection or relationship with the ground, such as contact, support, or reference.
- F. None of above. chosen
Provenance (5 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a292b23e16c819083a3d342fea5a473 |
completed | June 10, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:02 p.m.