Triple
T11269655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simons |
E266776
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Symons |
E907896
|
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: Symons | Statement: [Simons, hasVariant, Symons]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Symons Context triple: [Simons, hasVariant, Symons]
-
A.
Symons
chosen
Symons is a surname most notably associated with Donald Symons, an influential evolutionary psychologist known for his work on human sexuality.
-
B.
Simonds
Simonds is a surname most notably associated with Canadian Lieutenant-General Guy Simonds, a prominent military commander during the Second World War.
-
C.
Simmons
Simmons is a common English-language surname borne by numerous notable individuals across fields such as entertainment, sports, academia, and business.
-
D.
Simonis
Simonis is a major Brussels Metro interchange station serving multiple lines in the northwest of Brussels, Belgium.
-
E.
Symon
Symon is a given name most notably borne by Symon Petliura, a Ukrainian political leader and statesman of the early 20th century.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94f60d48190bc925c3cb88641a8 |
completed | April 9, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4ccdf9e0c819098a921146e8d6e30 |
completed | April 19, 2026, 12:38 p.m. |
Created at: April 8, 2026, 9:31 p.m.