Triple
T14134318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Cassin |
E350249
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Cassin |
E31114
|
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: Cassin | Statement: [John Cassin, familyName, Cassin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cassin Context triple: [John Cassin, familyName, Cassin]
-
A.
Cassin
chosen
Cassin is a French surname most notably borne by René Cassin, a Nobel Peace Prize–winning jurist and co-author of the Universal Declaration of Human Rights.
-
B.
Chabot
Chabot is a surname most notably associated with Anthony Chabot, a 19th-century entrepreneur and pioneer in California’s water supply and hydraulic mining industries.
-
C.
McNiven
McNiven is a surname of likely Scottish or Irish origin, often considered a variant of the name Niven.
-
D.
Michell
Michell is a given name and surname that functions as a variant spelling of Mitchell.
-
E.
Lander
Lander is a surname most notably associated with Frederick W. Lander, a 19th-century American civil engineer, explorer, and Union Army general.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610e949c8190852d336c9d12bfd0 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdf14439c81908b2a9999a35cc346 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 9, 2026, 11:45 p.m.