Triple
T14777857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abraham Pierson |
E347309
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pierson |
E310381
|
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: Pierson | Statement: [Abraham Pierson, familyName, Pierson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pierson Context triple: [Abraham Pierson, familyName, Pierson]
-
A.
Pierson
chosen
Pierson is a Dutch surname most notably associated with Nicolaas Pierson, a former Prime Minister of the Netherlands and economist.
-
B.
Piersonn
Piersonn is a variant spelling of the surname Pierson, which is of English and French origin and typically means "son of Piers" or "son of Peter."
-
C.
Blakely
Blakely is a given name and surname of English origin that has become popular as a modern unisex first name.
-
D.
Rylands
Rylands is a residential area in Nottinghamshire, England, commonly associated with the nearby town of Beeston.
-
E.
Rylands
Rylands is a locality within the Croydon Central area of the London Borough of Croydon in England.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec817c39081909b08a0ffdfce9936 |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0cff0474819092e8447f2f13cf59 |
completed | May 8, 2026, 4:19 p.m. |
Created at: April 10, 2026, 1:31 a.m.