Triple
T7865839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanley Corrsin |
E182611
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Corrsin |
E182611
|
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: Corrsin | Statement: [Stanley Corrsin, familyName, Corrsin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Corrsin Context triple: [Stanley Corrsin, familyName, Corrsin]
-
A.
Corrsin
chosen
Corrsin is a surname most notably associated with Stanley Corrsin, an influential American fluid dynamicist known for his work on turbulence.
-
B.
Cairon
Cairon is a small commune in the Calvados department of the Normandy region in northwestern France.
-
C.
Kiloran
Kiloran is a small coastal settlement on the Scottish island of Colonsay, known for its scenic bay and sandy beach.
-
D.
Vindrey
Vindrey is a rural locality in Russia notable as the birthplace of Soviet Marshal Sergei Akhromeyev.
-
E.
Corrin
Corrin is the customizable main protagonist of Fire Emblem Fates, a dragon-blooded royal torn between rival kingdoms whose choices shape the game's branching story.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3844eacc81908f8e1e5fc4dafec8 |
completed | March 31, 2026, 2:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbdf6fb33881908cf7bd68915aa6b4 |
completed | March 31, 2026, 2:51 p.m. |
Created at: March 30, 2026, 4:54 p.m.