Triple
T8464286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willis Van Devanter |
E200120
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Willis |
E31141
|
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: Willis | Statement: [Willis Van Devanter, givenName, Willis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Willis Context triple: [Willis Van Devanter, givenName, Willis]
-
A.
Willis
chosen
Willis is a masculine given name and surname of English origin, often considered a variant or cognate of the name Wilson.
-
B.
Sullivan
Sullivan is a common Irish surname that has been borne by numerous notable figures in politics, arts, sports, and other fields.
-
C.
Sullivan
Sullivan is a shortened name for the international law firm Sullivan & Worcester LLP, known for its corporate, tax, and financial legal services.
-
D.
Wayne
Wayne is a masculine given name of English origin commonly used in the United States and other English-speaking countries.
-
E.
Wayne
Wayne is a suburban community in Pennsylvania’s Main Line region, known for its residential neighborhoods and commuter access to Philadelphia.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a39bd48190b72be7e03cff323b |
completed | March 31, 2026, 3:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce39d5f50081908e273d5286a0d397 |
completed | April 2, 2026, 9:41 a.m. |
Created at: March 30, 2026, 6:11 p.m.