Triple
T1084053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trevi Fountain |
E24010
|
entity |
| Predicate | districtNameOrigin |
P24038
|
FINISHED |
| Object | Trevi from "Trivium" meaning three streets |
—
|
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: Trevi from "Trivium" meaning three streets | Statement: [Trevi Fountain, districtNameOrigin, Trevi from "Trivium" meaning three streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: districtNameOrigin Context triple: [Trevi Fountain, districtNameOrigin, Trevi from "Trivium" meaning three streets]
-
A.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
B.
countyName
Indicates the specific name assigned to a county in which an entity is located or with which it is associated.
-
C.
regionName
Indicates the name assigned to a specific geographic or administrative region.
-
D.
districtBasedOn
Indicates that one district is defined, derived, or established based on the boundaries, characteristics, or structure of another entity or area.
-
E.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
- F. None of above. chosen
Provenance (4 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9608bac819085196cc0f8fbb2e7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.