Triple
T13555266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Goddard |
E323754
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Goddard |
E399054
|
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: Goddard | Statement: [Victor Goddard, familyName, Goddard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goddard Context triple: [Victor Goddard, familyName, Goddard]
-
A.
Goddard
chosen
Goddard is a surname most famously associated with Robert H. Goddard, the American physicist and engineer regarded as the father of modern rocketry.
-
B.
Goddard
Goddard is Jimmy Neutron’s loyal robotic dog companion from the animated franchise "The Adventures of Jimmy Neutron: Boy Genius."
-
C.
Yangel
Yangel is a Ukrainian surname most notably associated with Mikhail Yangel, a prominent Soviet rocket engineer and designer.
-
D.
Borman
Borman is a surname most notably associated with Frank Borman, the American astronaut who commanded the historic Apollo 8 mission orbiting the Moon.
-
E.
McNiven
McNiven is a surname of likely Scottish or Irish origin, often considered a variant of the name Niven.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaff3063c8190bd20149b3f7df352 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75da95b7c8190af4fae155f01d3af |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.