Triple
T2651275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burn Gorman |
E53903
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Gorman |
E53904
|
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: Gorman | Statement: [Burn Gorman, familyName, Gorman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gorman Context triple: [Burn Gorman, familyName, Gorman]
-
A.
Gorman
chosen
Gorman is a surname most notably associated with English actor Burn Gorman, known for his roles in film and television.
-
B.
Garner
Garner is a surname most notably associated with John Nance Garner, the 32nd vice president of the United States under Franklin D. Roosevelt.
-
C.
Stevens
Stevens is a common English-language surname borne by numerous notable individuals across fields such as sports, politics, arts, and academia.
-
D.
Hamill
Hamill is the surname of Mark Hamill, the American actor best known for portraying Luke Skywalker in the Star Wars film series.
-
E.
Willard
Willard is a masculine given name of Old English origin meaning "resolute" or "strong-willed."
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd93071248190820197936e3167f7 |
completed | March 7, 2026, 7:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af98cc2d9881908556b915a1870c02 |
completed | March 10, 2026, 4:06 a.m. |
Created at: March 6, 2026, 9:53 p.m.