Triple
T4957036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold Briggs |
E111308
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Briggs |
E186099
|
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: Briggs | Statement: [Harold Briggs, familyName, Briggs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Briggs Context triple: [Harold Briggs, familyName, Briggs]
-
A.
Briggs
chosen
Briggs is a surname most prominently associated with Lance Briggs, a former NFL linebacker best known for his career with the Chicago Bears.
-
B.
Humphreys
Humphreys is a small unincorporated community located within Lea County in southeastern New Mexico.
-
C.
Bridgman
Bridgman is a surname most notably associated with American physicist and Nobel laureate Percy Williams Bridgman, a pioneer in high-pressure physics.
-
D.
Nortrup
Nortrup is a small municipality in Lower Saxony, Germany, situated within the Artland region.
-
E.
Oberholtzer
Oberholtzer is a German-origin surname, often associated with Mennonite and Amish families, that serves as a variant of the Overholt family name.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d6ba9c8190932f8d81240c3f56 |
completed | March 20, 2026, 4:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be81de17748190a26abda7d3703b8e |
completed | March 21, 2026, 11:32 a.m. |
Created at: March 20, 2026, 1:32 p.m.