Triple
T29438995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appian Aqueduct |
E746658
|
entity |
| Predicate | entersCityAt |
P128436
|
FINISHED |
| Object | Porta Maggiore area of Rome |
—
|
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: Porta Maggiore area of Rome | Statement: [Appian Aqueduct, entersCityAt, Porta Maggiore area of Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entersCityAt Context triple: [Appian Aqueduct, entersCityAt, Porta Maggiore area of Rome]
-
A.
enteredCityAt
chosen
Indicates that an entity arrived in or crossed into a specific city at a particular point in time.
-
B.
enteredCity
Indicates that an entity has moved into or arrived within the boundaries of a specific city.
-
C.
enteredServiceInCity
Indicates that an entity began its operational service or official use within a specified city.
-
D.
servesAsMainPortOfEntryFor
Indicates that one location functions as the primary gateway or access point through which another entity typically enters a region or system.
-
E.
accessFromCity
Indicates that there is a way to reach or enter a place starting from a specified city.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 3:19 p.m.