Triple
T16410711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Shae Perring |
E398554
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Perring |
E266129
|
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: Perring | Statement: [John Shae Perring, familyName, Perring]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perring Context triple: [John Shae Perring, familyName, Perring]
-
A.
Perring
chosen
Perring was a 19th-century British engineer and Egyptologist known for his early surveys and studies of Egyptian pyramids.
-
B.
Prendergast
Prendergast is an Irish surname historically associated with families of Norman origin that settled in Ireland.
-
C.
Petrie
Petrie is a suburban town in Queensland, Australia, known for its location along the North Pine River and its role as a residential and educational hub within the Moreton Bay region.
-
D.
Petrie
Petrie is a surname most notably associated with Geoff Petrie, a former American professional basketball player and executive.
-
E.
Pippard
Pippard is an English surname most notably associated with physicist Sir Brian Pippard, a pioneer in the study of superconductivity.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328731a408190b38dcab0b7bb65ff |
completed | April 18, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c66d41481909340f247f6e5393f |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 5:09 a.m.