Triple
T31146956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio XIV Transtiberim |
E793950
|
entity |
| Predicate | containedAcrossFrom |
P94992
|
FINISHED |
| Object | Campus Martius |
—
|
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: Campus Martius | Statement: [Regio XIV Transtiberim, containedAcrossFrom, Campus Martius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedAcrossFrom Context triple: [Regio XIV Transtiberim, containedAcrossFrom, Campus Martius]
-
A.
occursAcross
Indicates that an event, process, or condition extends over or takes place throughout a specified span, range, or set of contexts.
-
B.
across
chosen
Indicates a spatial relationship where one entity is on the opposite side of, or extending from one side to the other side of, another entity or area.
-
C.
usedAcross
Indicates that something is utilized or applied in multiple different contexts, locations, or domains.
-
D.
crossedFrom
Indicates that an entity moved across a boundary or dividing line starting from a specified origin location or side.
-
E.
expandedAcross
Indicates that something has grown or extended so that it now spans or covers multiple areas, regions, or segments.
- 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_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: April 29, 2026, 9:06 p.m.