Triple
T20302943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ros Beiaard legend |
E505530
|
entity |
| Predicate | hasMainCharacter |
P1183
|
FINISHED |
| Object | Ros Beiaard |
—
|
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: Ros Beiaard | Statement: [Ros Beiaard legend, hasMainCharacter, Ros Beiaard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ros Beiaard Context triple: [Ros Beiaard legend, hasMainCharacter, Ros Beiaard]
-
A.
Ros Beiaard
chosen
Ros Beiaard is a legendary giant horse from Flemish folklore, famously celebrated in the decennial Ros Beiaard procession in Dendermonde, Belgium.
-
B.
Reuver
Reuver is a village in the Dutch province of Limburg, situated along the River Meuse and served by the Maaslijn railway.
-
C.
Beerzelberg
Beerzelberg is a modest hill in Belgium known as the highest natural point in Antwerp Province.
-
D.
Ropscha
Ropscha is a rural locality in Leningrad Oblast, Russia, historically known for its imperial estate associated with the Russian royal family.
-
E.
Bonte
Bonte is a German surname most notably borne by Friedrich Bonte, a Kriegsmarine officer during World War II.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6773e0864819095d272659cd2074d |
completed | April 20, 2026, 6:58 p.m. |
Created at: April 16, 2026, 11:17 a.m.