Triple
T3350181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liège–Bastogne–Liège 1966 |
E70471
|
entity |
| Predicate | isMonumentClassic |
P47397
|
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: [Liège–Bastogne–Liège 1966, isMonumentClassic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonumentClassic Context triple: [Liège–Bastogne–Liège 1966, isMonumentClassic, true]
-
A.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
B.
monumentState
Indicates that a monument is located within, or officially associated with, a particular state or state-level administrative region.
-
C.
monumentStyle
Indicates the architectural or artistic style characterizing a monument in relation to that monument.
-
D.
monumentStatus
Indicates the official designation or condition of an entity as a monument, such as whether it is recognized, protected, or classified under heritage or preservation status.
-
E.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb21f3ae48190a33530712da01bc3 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.