Triple
T33193173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James J. Jeffries |
E849666
|
entity |
| Predicate | locationOfFightWithJackJohnson |
P70420
|
FINISHED |
| Object | Reno, Nevada, United States |
E171705
|
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: Reno, Nevada, United States | Statement: [James J. Jeffries, locationOfFightWithJackJohnson, Reno, Nevada, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFightWithJackJohnson Context triple: [James J. Jeffries, locationOfFightWithJackJohnson, Reno, Nevada, United States]
-
A.
fightDateWithJackJohnson
Indicates the date on which an entity had a fight with Jack Johnson.
-
B.
fightsAtLocation
chosen
Indicates that a fighting interaction between entities occurs at a specified location.
-
C.
allegedLocationOfDuel
Indicates the place where a duel is claimed or reported to have occurred, without confirming that it actually took place there.
-
D.
secondFightLocation
Indicates the location where the second fight or confrontation between the involved entities takes place.
-
E.
locationOfRivalry
Indicates the place or setting where a rivalry between entities occurs or is centered.
- F. None of above.
Provenance (4 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a036f0569cc8190a8ac7f4e07145d15 |
completed | May 12, 2026, 6:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3525d702f08190a03ce5e00d842c9a |
completed | June 19, 2026, 11:19 a.m. |
| PD | Predicate disambiguation | batch_6a036c42cf2481908760c7d48b9fc001 |
completed | May 12, 2026, 6:06 p.m. |
Created at: May 1, 2026, 1:29 a.m.