Triple
T6107081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endeavor Group Holdings |
E136142
|
entity |
| Predicate | subsidiary |
P258
|
FINISHED |
| Object | PBR |
E568751
|
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: PBR | Statement: [Endeavor Group Holdings, subsidiary, PBR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PBR Context triple: [Endeavor Group Holdings, subsidiary, PBR]
-
A.
PBR
PBR is the Indian Railways station code for Porbandar railway station in Gujarat, India.
-
B.
PBR
chosen
PBR (Professional Bull Riders) is a premier international bull riding organization and sports league featuring top riders competing in high-adrenaline events.
-
C.
PBD
PBD is the IATA airport code for Porbandar Airport, a domestic airport serving the city of Porbandar in the Indian state of Gujarat.
-
D.
PB
PB is the official vehicle registration code for the Brazilian state of Paraíba.
-
E.
PB
PB is the post-nominal abbreviation used to denote recipients of the Padma Bhushan, one of India’s highest civilian honors.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b806bd48190b6f020af3391adb8 |
completed | March 22, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c13598c54c8190b3701de83005875c |
completed | March 23, 2026, 12:44 p.m. |
Created at: March 22, 2026, 4:13 p.m.