Triple
T3246034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Parsons |
E68068
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Parsons |
E200177
|
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: Parsons | Statement: [Jim Parsons, familyName, Parsons]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parsons Context triple: [Jim Parsons, familyName, Parsons]
-
A.
Parsons
chosen
Parsons is a surname of English origin borne by numerous notable individuals across politics, arts, science, and other fields.
-
B.
Parsons
Parsons is a residential neighborhood located within the city of Wilkes-Barre in northeastern Pennsylvania.
-
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.
Wyman-Gordon
Wyman-Gordon is an industrial manufacturer known for producing high-strength forged components, particularly for the aerospace and energy industries.
-
E.
Stevens
Stevens is a common English-language surname borne by numerous notable individuals across fields such as sports, politics, arts, and academia.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf1a96148190b63bf46209712707 |
completed | March 8, 2026, 5:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2775f76988190bfaaaabce63f6f6b |
completed | March 12, 2026, 8:20 a.m. |
Created at: March 8, 2026, 3:09 p.m.