Triple
T20133014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Irvine |
E490946
|
entity |
| Predicate | surnameVariant |
P16885
|
FINISHED |
| Object | Irwin |
—
|
NE NERFINISHED |
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: Irwin | Statement: [Clan Irvine, surnameVariant, Irwin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Irwin Context triple: [Clan Irvine, surnameVariant, Irwin]
-
A.
Irwin
chosen
Irwin is a masculine given name and surname of English origin, historically associated with various notable figures in fields such as entertainment, science, and politics.
-
B.
Irvin
Irvin is a surname most prominently associated with former NFL wide receiver and sports commentator Michael Irvin.
-
C.
Darvin
Darvin is a masculine given name most notably borne by former NBA player and current basketball coach Darvin Ham.
-
D.
Imrie
Imrie is a Scottish surname borne by various notable individuals, including actors, athletes, and public figures.
-
E.
Vargo
Vargo is a surname most notably associated with Ed Vargo, an American Major League Baseball umpire.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66763ee908190af64af31b4ca2377 |
completed | April 20, 2026, 5:50 p.m. |
Created at: April 11, 2026, 11:32 p.m.