Triple
T30922649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lier beguinage |
E787769
|
entity |
| Predicate | UNESCOSerialPropertyName |
P172535
|
FINISHED |
| Object | Flemish Béguinages |
—
|
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: Flemish Béguinages | Statement: [Lier beguinage, UNESCOSerialPropertyName, Flemish Béguinages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOSerialPropertyName Context triple: [Lier beguinage, UNESCOSerialPropertyName, Flemish Béguinages]
-
A.
UNESCOSerialNomination
Indicates that multiple geographically or culturally related sites are jointly nominated as a single serial property on the UNESCO World Heritage List.
-
B.
officialNameUNESCO
Indicates the official name of an entity as recognized or designated by UNESCO.
-
C.
UNESCOSiteNameLanguage
Indicates the language in which a UNESCO site’s name is expressed.
-
D.
inscriptionNumberUNESCO
Indicates the unique identification number assigned to an item by UNESCO upon its official inscription or listing.
-
E.
UNESCOSiteType
Indicates the classification of a UNESCO World Heritage Site according to its type (e.g., cultural, natural, or mixed).
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 29, 2026, 8:51 p.m.