Triple
T31146972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio XIV Transtiberim |
E793950
|
entity |
| Predicate | containedHarbor |
P3007
|
FINISHED |
| Object | Portus Transtiberinus |
—
|
NE NERFINISHED |
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: Portus Transtiberinus | Statement: [Regio XIV Transtiberim, containedHarbor, Portus Transtiberinus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedHarbor Context triple: [Regio XIV Transtiberim, containedHarbor, Portus Transtiberinus]
-
A.
harbor
Indicates providing shelter, protection, or refuge for someone or something, often by keeping them in a safe or hidden place.
-
B.
hasHarbor
chosen
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
C.
enteredHarbour
Indicates that an entity has moved into and arrived within the boundaries of a harbour.
-
D.
sharesHarborWith
Indicates that two entities use or are associated with the same harbor.
-
E.
harborType
Indicates the specific kind or classification of a harbor associated with an entity.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: April 29, 2026, 9:06 p.m.