Triple
T6808271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Maud of Wales |
E156364
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Maud |
E117170
|
NE 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: Maud | Statement: [Princess Maud of Wales, givenName, Maud]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maud Context triple: [Princess Maud of Wales, givenName, Maud]
-
A.
Maud
chosen
Maud is a feminine given name of Germanic origin, historically borne by European royalty and nobility.
-
B.
Maud
Maud was a Norwegian polar exploration ship used by Roald Amundsen during his Arctic expeditions in the early 20th century.
-
C.
Maud
Maud is a small village in Aberdeenshire, Scotland, known historically as a rural railway junction and agricultural center.
-
D.
Milbanke
Milbanke is an English aristocratic family name historically associated with the wife of poet Lord Byron, Annabella Milbanke.
-
E.
Ethel
Ethel is a feminine given name of Old English origin, historically popular in English-speaking countries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30b56c48190a5b244ea7e0c669a |
completed | March 27, 2026, 6:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71aa5411c81908d05bef3213b39f1 |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:16 p.m.