Triple
T28261699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Denkmalliste |
E712598
|
entity |
| Predicate | isOfficialRegister |
P53863
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Austrian Denkmalliste, isOfficialRegister, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficialRegister Context triple: [Austrian Denkmalliste, isOfficialRegister, true]
-
A.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
-
B.
officialRegisterOf
chosen
Indicates that one entity serves as the authoritative, formally maintained record or registry for another entity.
-
C.
areOfficialIn
Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
-
D.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
-
E.
isOfficialOfficeOf
Indicates that one entity serves as the formally recognized office or headquarters associated with another entity.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64419e5f881908d08370af0445383 |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:12 p.m.