Triple
T3834449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bovinae |
E91094
|
entity |
| Predicate | includesTaxon |
P1393
|
FINISHED |
| Object | Bos |
E234057
|
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: Bos | Statement: [Bovinae, includesTaxon, Bos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bos Context triple: [Bovinae, includesTaxon, Bos]
-
A.
Bos
Bos is a Dutch surname most notably borne by Bert Bos, a computer scientist and co-creator of the CSS web standard.
-
B.
Bos
chosen
Bos is a genus of large bovids that includes domestic cattle and several wild species such as gaur, banteng, and yak.
-
C.
Bor
Bor is a town in Nizhny Novgorod Oblast, Russia, located on the left bank of the Volga River opposite the city of Nizhny Novgorod and known for its industrial and river transport significance.
-
D.
Bori
Bori is a prominent urban center in Nigeria’s Rivers State, serving as an important commercial and administrative hub for the surrounding region.
-
E.
Böri
Böri was a lesser-known member of the Mongol imperial family, recognized primarily as a sibling of the Great Khan Möngke.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8a27688190866bc41441e2260c |
completed | March 9, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b503ffab6c81909d64a11511693c1f |
completed | March 14, 2026, 6:45 a.m. |
Created at: March 9, 2026, 3:18 p.m.