Triple
T5097778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guy Edward Pearce |
E114909
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pearce |
E155807
|
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: Pearce | Statement: [Guy Edward Pearce, familyName, Pearce]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pearce Context triple: [Guy Edward Pearce, familyName, Pearce]
-
A.
Pearce
chosen
Pearce is a surname and given name of English origin, commonly considered a variant of "Pierce" and ultimately derived from the name "Peter."
-
B.
Rowan
Rowan is a masculine given name of Irish and Scottish origin, commonly associated with the actor and comedian Rowan Atkinson.
-
C.
Morgan
Morgan is the middle name of the renowned English novelist and essayist E. M. Forster.
-
D.
Morgan
Morgan is a prominent American banking and finance family name most famously associated with financier J. P. Morgan and the powerful House of Morgan banking dynasty.
-
E.
Morgan
Morgan is a common English surname borne by numerous notable individuals across fields such as science, finance, and entertainment.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7567d21081909227ed8f08b74c71 |
completed | March 20, 2026, 4:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beba8529ec8190bb1e97eb1044c899 |
completed | March 21, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:40 p.m.