Triple
T14889382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neusatz |
E359712
|
entity |
| Predicate | modernCityIs |
P116212
|
FINISHED |
| Object | major cultural center |
—
|
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: major cultural center | Statement: [Neusatz, modernCityIs, major cultural center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCityIs Context triple: [Neusatz, modernCityIs, major cultural center]
-
A.
modernCityBuiltAround
Indicates that a contemporary or recently developed city has been constructed encircling or surrounding a particular central feature, structure, or area.
-
B.
containsModernCity
Indicates that one geographic or administrative region includes within its boundaries a currently existing modern city.
-
C.
majorUrbanCenterIn
Indicates that a city or metropolitan area functions as a primary or significant urban center within the specified region or administrative unit.
-
D.
city2
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
-
E.
metropolitan
Indicates that a location is part of, belongs to, or lies within a specified metropolitan (urban) area.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f6cf5c8190b6b28f58fafe5d59 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4c76e481909c0aa8d1a978e8d5 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 2:09 a.m.