Triple
T37745758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of the Diocese of Freising |
E940838
|
entity |
| Predicate | historicalUseStatus |
P28623
|
FINISHED |
| Object | historical |
—
|
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: historical | Statement: [coat of arms of the Diocese of Freising, historicalUseStatus, historical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalUseStatus Context triple: [coat of arms of the Diocese of Freising, historicalUseStatus, historical]
-
A.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
historicalStatusOf
chosen
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
C.
historicalUseInCountry
Indicates that something has been used or practiced within a specific country during a past historical period.
-
D.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
E.
hasHistoricalUsageIn
Indicates that something has been used or practiced within a particular historical period, context, or tradition.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01b50490e481908eb1d675561fdde2 |
completed | May 11, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_6a01b44b106481908aa98a3f1eb2c119 |
completed | May 11, 2026, 10:49 a.m. |
Created at: May 3, 2026, 4:19 p.m.