Triple
T31077551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forum Holitorium |
E792005
|
entity |
| Predicate | hasTopographicalCategory |
P80940
|
FINISHED |
| Object | Roman topography |
—
|
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: Roman topography | Statement: [Forum Holitorium, hasTopographicalCategory, Roman topography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopographicalCategory Context triple: [Forum Holitorium, hasTopographicalCategory, Roman topography]
-
A.
topographicalCategory
chosen
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
-
B.
hasTopographicContext
Indicates that one entity is related to or characterized by a particular topographic or physical landscape context.
-
C.
hasTopographicalRole
Indicates that an entity serves a specific functional or positional role within a topographical or spatial context.
-
D.
associatedTopography
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
-
E.
isDerivedFromTopographicalFeature
Indicates that something originates from, is based on, or is obtained from a specific topographical or geographic feature.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 29, 2026, 9:02 p.m.