Triple
T16821187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurice Stans |
E408895
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Stans |
E408895
|
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: Stans | Statement: [Maurice Stans, familyName, Stans]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stans Context triple: [Maurice Stans, familyName, Stans]
-
A.
Stans
chosen
Stans is a surname most notably associated with Maurice Stans, a U.S. Secretary of Commerce and key figure in the Nixon administration and Watergate scandal.
-
B.
Stans
Stans is a historic Swiss town in central Switzerland, known as the capital of the canton of Nidwalden and for its picturesque Alpine setting.
-
C.
STAN
STAN is the London Stock Exchange ticker symbol for Standard Chartered, a major British multinational banking and financial services company.
-
D.
Sten
Sten is a Scandinavian male given name of Old Norse origin, commonly associated with Sweden and meaning "stone."
-
E.
Tyoply Stan
Tyoply Stan is a Moscow Metro station located in the southwestern part of Moscow, Russia.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e6b59c8190ad562a80e71ce54c |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b29a3854819099eed580eea5d84d |
completed | May 10, 2026, 4:30 p.m. |
Created at: April 10, 2026, 5:23 a.m.