Triple
T1456100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pat Nixon |
E31403
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Pat |
E111527
|
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: Pat | Statement: [Pat Nixon, nickname, Pat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pat Context triple: [Pat Nixon, nickname, Pat]
-
A.
Pat
chosen
Pat is the commonly used short form of the given name Patrick, often used as a casual or familiar nickname.
-
B.
Pete
Pete is the nickname of Grover Cleveland Alexander, a Hall of Fame Major League Baseball pitcher and one of the greatest hurlers of the early 20th century.
-
C.
Pete
Pete is a common masculine given name, typically used as a familiar or informal form of the name Peter.
-
D.
Pal
Pal is an Indian surname notably borne by Bipin Chandra Pal, a prominent nationalist leader in the Indian independence movement.
-
E.
Jack
Jack is a common masculine given name, often used as a familiar form of John and widely featured in English-language literature and popular culture.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c581714881909bf4c2bad9645176 |
completed | March 1, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad0e746b64819091079ff26a60a12e |
completed | March 8, 2026, 5:51 a.m. |
Created at: March 1, 2026, 8 p.m.