Triple
T610991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiber |
E12096
|
entity |
| Predicate | containedBy |
P12261
|
FINISHED |
| Object | Tiber embankment walls in Rome |
—
|
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: Tiber embankment walls in Rome | Statement: [Tiber, containedBy, Tiber embankment walls in Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedBy Context triple: [Tiber, containedBy, Tiber embankment walls in Rome]
-
A.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
B.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
-
C.
withinFeature
chosen
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
D.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df7c088819082eb70de4f0f4fbf |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cfa7b4481909bec7a5fd3e98c65 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.