Triple
T1552530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfred P. Sloan |
E33124
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Sloan |
E33124
|
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: Sloan | Statement: [Alfred P. Sloan, familyName, Sloan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sloan Context triple: [Alfred P. Sloan, familyName, Sloan]
-
A.
Sloan
chosen
Sloan is a surname most notably associated with Alfred P. Sloan, the influential long-time president and chairman of General Motors.
-
B.
Sloan
Sloan is a small unincorporated community in Clark County, Nevada, located just south of Las Vegas along Interstate 15.
-
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.
Vivanco
Vivanco is a Spanish-language surname of likely Iberian origin borne by various notable individuals.
-
E.
Sullivan
Sullivan is a shortened name for the international law firm Sullivan & Worcester LLP, known for its corporate, tax, and financial legal services.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9086aed94819085c8194b4127c278 |
completed | March 5, 2026, 4:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad370b9b4c819087d04abead99e81e |
completed | March 8, 2026, 8:44 a.m. |
Created at: March 4, 2026, 7:26 p.m.