Triple
T20861390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muriel Heslop |
E513625
|
entity |
| Predicate | hasGivenName |
P17
|
FINISHED |
| Object | Muriel |
—
|
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: Muriel | Statement: [Muriel Heslop, hasGivenName, Muriel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Muriel Context triple: [Muriel Heslop, hasGivenName, Muriel]
-
A.
Muriel
chosen
Muriel is a feminine given name of French origin that has been borne by various notable figures, including politicians, writers, and artists.
-
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.
Maud
Maud is a feminine given name of Germanic origin, historically borne by European royalty and nobility.
-
E.
Eulalie
Eulalie is a feminine given name of French origin, derived from the Latin "Eulalia" meaning "well-spoken" or "eloquent."
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3ad3d1c8190be2fe35a85f2447c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 12:44 p.m.