Triple
T28841104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Heart of Austria |
E728315
|
entity |
| Predicate | hasEquivalentNickname |
P28716
|
FINISHED |
| Object | Grünes Herz Österreichs |
—
|
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: Grünes Herz Österreichs | Statement: [Green Heart of Austria, hasEquivalentNickname, Grünes Herz Österreichs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEquivalentNickname Context triple: [Green Heart of Austria, hasEquivalentNickname, Grünes Herz Österreichs]
-
A.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
B.
hasNicknameStatus
Indicates that an entity holds a particular status or classification specifically related to its nickname.
-
C.
usesNicknameIn
Indicates that one entity refers to another entity by a specific nickname within a particular context or setting.
-
D.
hasNicknameForm
Indicates that one entity is a nickname or informal variant form of another entity’s name.
-
E.
isNickname
chosen
Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another name.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65972569081909bb61c83b7f71c59 |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:40 a.m.