Triple
T17139815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Arison |
E415933
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Arison |
E415933
|
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: Arison | Statement: [Ted Arison, familyName, Arison]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arison Context triple: [Ted Arison, familyName, Arison]
-
A.
Arison
chosen
Arison is a surname most prominently associated with the Israeli-American Arison family, known for its major roles in global business and philanthropy, including leadership of Carnival Corporation.
-
B.
Ascherson
Ascherson is a surname most notably associated with British actress Renée Asherson.
-
C.
Aaroni
Aaroni is a Finnish diminutive or affectionate variant of the male given name Aaro.
-
D.
Ariyon
Ariyon is a given name most notably borne by British actor and director Ariyon Bakare.
-
E.
Natanson
Natanson is a surname most notably associated with Mark Natanson, a prominent Russian revolutionary and political activist of the late 19th and early 20th centuries.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d318a88190aae8d776376c8053 |
completed | April 18, 2026, 9:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a014152da008190bbbff4147cfd8c5b |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:36 a.m.