Triple
T8389881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Petrie |
E197913
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Petrie |
E376764
|
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: Petrie | Statement: [Mark Petrie, hasFamilyName, Petrie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petrie Context triple: [Mark Petrie, hasFamilyName, Petrie]
-
A.
Petrie
chosen
Petrie is a surname most notably associated with Geoff Petrie, a former American professional basketball player and executive.
-
B.
Pinchbeck
Pinchbeck is a village and civil parish in the South Holland district of Lincolnshire, England, known for its agricultural surroundings and proximity to the town of Spalding.
-
C.
Polton
Polton is a small village in Midlothian, Scotland, situated near the River North Esk and historically associated with paper milling.
-
D.
Shadbolt
Shadbolt is a surname most notably associated with Sir Nigel Shadbolt, a prominent British computer scientist and artificial intelligence researcher.
-
E.
Perring
Perring was a 19th-century British engineer and Egyptologist known for his early surveys and studies of Egyptian pyramids.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb810ac380819095bd67f0555ac2a8 |
completed | March 31, 2026, 8:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde84427dc8190925150b5d52bc9a0 |
completed | April 2, 2026, 3:53 a.m. |
Created at: March 30, 2026, 6:03 p.m.