Triple
T34905538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wien Neêrlands Bloed |
E1006715
|
entity |
| Predicate | hasTitleInModernSpelling |
P114637
|
FINISHED |
| Object | Wien Neerlands Bloed |
—
|
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: Wien Neerlands Bloed | Statement: [Wien Neêrlands Bloed, hasTitleInModernSpelling, Wien Neerlands Bloed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleInModernSpelling Context triple: [Wien Neêrlands Bloed, hasTitleInModernSpelling, Wien Neerlands Bloed]
-
A.
hasTitleInModernEnglish
Indicates that an entity is associated with a specific title expressed in modern English.
-
B.
hasTitleInEnglishOrthography
chosen
Indicates that an entity has a specific title expressed using English spelling and writing conventions.
-
C.
hasTitleInRevisedRomanization
Indicates that an entity has a specific title expressed using the Revised Romanization system for Korean.
-
D.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
E.
spellingOfNameInTitle
Indicates that the specific spelling of a person's or entity's name appears in the title of a work or resource.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4 p.m.