Triple
T37696500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigil of the Princes for King George V in 1936 |
E938942
|
entity |
| Predicate | hasMonarchHonoured |
P29297
|
FINISHED |
| Object | George V |
—
|
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: George V | Statement: [Vigil of the Princes for King George V in 1936, hasMonarchHonoured, George V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonarchHonoured Context triple: [Vigil of the Princes for King George V in 1936, hasMonarchHonoured, George V]
-
A.
hasMonarchFrom
Indicates that a political entity is ruled by, or has as its monarch, a specific individual from a given time or context.
-
B.
monarchCelebrated
chosen
Indicates that a monarch is honored, commemorated, or publicly celebrated in some manner.
-
C.
confirmedMonarch
Indicates that an entity has been formally recognized and validated as the legitimate monarch, typically through an official confirmation process.
-
D.
namedForMonarch
Indicates that one entity bears a name derived from or given in honor of a monarch.
-
E.
monarchSubjectOf
Indicates that a monarch is the central topic or focus of a given statement, document, or informational 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: May 3, 2026, 4:18 p.m.