Triple
T14260659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Borman |
E353507
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Borman |
E353507
|
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: Borman | Statement: [Frank Borman, familyName, Borman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Borman Context triple: [Frank Borman, familyName, Borman]
-
A.
Borman
chosen
Borman is a surname most notably associated with Frank Borman, the American astronaut who commanded the historic Apollo 8 mission orbiting the Moon.
-
B.
Chesley
Chesley is a small rural community in Bruce County, Ontario, Canada, known for its agricultural surroundings and local manufacturing history.
-
C.
Goddard
Goddard is a surname most famously associated with Robert H. Goddard, the American physicist and engineer regarded as the father of modern rocketry.
-
D.
Goddard
Goddard is Jimmy Neutron’s loyal robotic dog companion from the animated franchise "The Adventures of Jimmy Neutron: Boy Genius."
-
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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de635534988190816fdfb315cd2a3f |
completed | April 14, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3260fdf88190b482480a17bd6674 |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:09 a.m.