Triple
T30922650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lier beguinage |
E787769
|
entity |
| Predicate | UNESCOSerialPropertyComponentCount |
P163004
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Lier beguinage, UNESCOSerialPropertyComponentCount, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOSerialPropertyComponentCount Context triple: [Lier beguinage, UNESCOSerialPropertyComponentCount, 13]
-
A.
UNESCOSerialPropertyName
Indicates that a site or component is identified by the specific name assigned to it within a UNESCO World Heritage serial property.
-
B.
heritageNumberOfComponents
chosen
Indicates the number of distinct components or parts that make up a given heritage item or entity.
-
C.
heritageSerialProperty
Indicates that a heritage site is part of a serial property, i.e., a group of related heritage components recognized collectively as a single inscription or designation.
-
D.
partOfSerialProperty
Indicates that a property belongs to, or is a component within, a larger serial or sequential collection of properties.
-
E.
UNESCOWorldHeritageSitesCount
Indicates the number of UNESCO World Heritage Sites associated with a given 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 8:51 p.m.