Triple
T30005021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercules monument |
E762284
|
entity |
| Predicate | iconicLandmarkOf |
P66917
|
FINISHED |
| Object | Kassel |
—
|
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: Kassel | Statement: [Hercules monument, iconicLandmarkOf, Kassel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconicLandmarkOf Context triple: [Hercules monument, iconicLandmarkOf, Kassel]
-
A.
primaryCityLandmarkOf
chosen
Indicates that a landmark is a principal or defining landmark associated with a specific city.
-
B.
emblematicBuildingLocation
Indicates that a building serves as a symbolic or representative landmark for a particular location or area.
-
C.
iconicFeature
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
-
D.
cityLandmarkID
Indicates that a specific landmark is uniquely identified as being located within a particular city.
-
E.
isUrbanLandmark
Indicates that a place or structure is recognized as a notable or significant landmark within an urban environment.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67951d2e48190b471e0d5f529e78c |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:42 p.m.