Triple
T20754553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Munroe |
E510812
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Munroe |
—
|
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: Munroe | Statement: [David Munroe, familyName, Munroe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Munroe Context triple: [David Munroe, familyName, Munroe]
-
A.
Munroe
chosen
Munroe is a surname of Scottish origin borne by various notable individuals across fields such as politics, sports, and the arts.
-
B.
Monro
Monro is a variant spelling of the Scottish surname Munro, historically associated with a Highland clan from Easter Ross.
-
C.
Monrow
Monrow is an alternative spelling of the name Monroe, which is commonly used as both a surname and given name and is associated with various notable people and places.
-
D.
McLure
McLure is a surname of Scottish origin, commonly considered a variant spelling of McClure.
-
E.
Whigham
Whigham is a surname most notably associated with American actor Shea Whigham, known for his character roles in film and television.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c22e0d288190ba924423af59d70d |
completed | April 21, 2026, 12:17 a.m. |
Created at: April 16, 2026, 12:34 p.m.