Triple
T28661483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valeria |
E725478
|
entity |
| Predicate | hasImportantCityToday |
P138593
|
FINISHED |
| Object | Budapest (Aquincum area) |
—
|
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: Budapest (Aquincum area) | Statement: [Valeria, hasImportantCityToday, Budapest (Aquincum area)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantCityToday Context triple: [Valeria, hasImportantCityToday, Budapest (Aquincum area)]
-
A.
presentDayCityIs
chosen
Indicates that one entity is the current, modern-day city corresponding to or located at the place represented by the other entity.
-
B.
hasFamousCity
Indicates that an entity possesses or is associated with a city that is widely recognized or renowned.
-
C.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
D.
isMajorCityIn
Indicates that a city is a primary or significant urban center located within a specified larger region or country.
-
E.
cityOn
Indicates that a city is geographically located on a specified landform, area, or administrative region.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 4:58 a.m.