Triple
T3818520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Kasdan |
E84315
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kasdan |
E124367
|
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: Kasdan | Statement: [Jonathan Kasdan, familyName, Kasdan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kasdan Context triple: [Jonathan Kasdan, familyName, Kasdan]
-
A.
Kasdan
chosen
Kasdan is a surname most notably associated with American screenwriter, director, and producer Lawrence Kasdan, known for his work on major films such as "The Empire Strikes Back" and "Raiders of the Lost Ark."
-
B.
Kadan
Kadan was a Mongol prince and military commander who played a key role in the Mongol invasions of Central and Eastern Europe in the 13th century.
-
C.
Kandan
Kandan is a locality within Beijing’s Fengtai District, known primarily as a residential and urban neighborhood area.
-
D.
Qadan
Qadan was a 13th-century Mongol military leader and prince of the Borjigin dynasty who led Mongol forces during their campaign in Poland.
-
E.
Kashshaya
Kashshaya was a Neo-Babylonian royal woman known primarily as the wife of King Amel-Marduk.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeea5e41ec81908ed7e1ccc2713622 |
completed | March 9, 2026, 3:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4fb43e1d481909a5b52cae5686179 |
completed | March 14, 2026, 6:08 a.m. |
Created at: March 9, 2026, 3:17 p.m.