Triple
T27015275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adolf Hitler Platz |
E680507
|
entity |
| Predicate | appliedToCurrentCountry |
P181121
|
FINISHED |
| Object | Slovenia |
—
|
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: Slovenia | Statement: [Adolf Hitler Platz, appliedToCurrentCountry, Slovenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToCurrentCountry Context triple: [Adolf Hitler Platz, appliedToCurrentCountry, Slovenia]
-
A.
locatedInCurrentCountry
Indicates that an entity is situated within the geographic boundaries of the country in which it is presently found.
-
B.
isSetInCountry
Indicates that something (such as an event, story, or scene) takes place within the geographical or political boundaries of a specified country.
-
C.
includesPresentCountry
Indicates that an entity (such as a region, organization, or grouping) currently contains or encompasses a specified country within its present composition or membership.
-
D.
correspondsToCountry
Indicates that one entity is associated with, matches, or represents a specific country.
-
E.
appliesToPersonNationality
Indicates that something is relevant or applicable specifically to a person’s nationality.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 27, 2026, 7:05 a.m.