Triple
T13435374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Bowman |
E320215
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bowman |
E799772
|
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: Bowman | Statement: [Bob Bowman, familyName, Bowman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bowman Context triple: [Bob Bowman, familyName, Bowman]
-
A.
Bowman
"Bowman" is a song by the Japanese rock band Ultra Q, known for its energetic style and modern alternative rock sound.
-
B.
Bowman
chosen
Bowman is a common English surname of occupational origin, historically referring to an archer or bowman.
-
C.
Bowe
Bowe is the surname of Riddick Bowe, an American former professional boxer and two-time world heavyweight champion.
-
D.
Bonger
Bonger is a Dutch surname most notably associated with Johanna van Gogh-Bonger, the key figure in preserving and promoting Vincent van Gogh’s artistic legacy.
-
E.
Borman
Borman is a surname most notably associated with Frank Borman, the American astronaut who commanded the historic Apollo 8 mission orbiting the Moon.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee29fec81908b07b4fca2922242 |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f739902d148190ac14ac66f1f9512f |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:40 p.m.