Triple
T30803789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kruckenkreuz |
E784441
|
entity |
| Predicate | countryOfProminentUse |
P55272
|
FINISHED |
| Object | Austria |
—
|
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: Austria | Statement: [Kruckenkreuz, countryOfProminentUse, Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfProminentUse Context triple: [Kruckenkreuz, countryOfProminentUse, Austria]
-
A.
primaryUseCountry
Indicates the country in which something is primarily used or most commonly utilized.
-
B.
countryOfSymbolicUse
Indicates the country in which something (such as a symbol, object, or element) is used in a symbolic or representative way.
-
C.
countryNameUsage
Indicates how a country’s name is used or applied in a particular context or representation.
-
D.
countryOrRegionOfPrevalence
chosen
Indicates the country or geographic region where something (such as a condition, practice, or phenomenon) is most commonly found or occurs most frequently.
-
E.
usedByCountriesWith
Indicates that something (such as an item, system, or practice) is utilized or employed by one or more specified countries in common.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: April 29, 2026, 8:42 p.m.