Triple
T25888665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball color barrier |
E652263
|
entity |
| Predicate | brokenInLeague |
P160297
|
FINISHED |
| Object | National League |
—
|
NE NERFINISHED |
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: National League | Statement: [Major League Baseball color barrier, brokenInLeague, National League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokenInLeague Context triple: [Major League Baseball color barrier, brokenInLeague, National League]
-
A.
brokenIn
Indicates that an object or system has become nonfunctional or damaged while located within or inside a particular place, context, or container.
-
B.
brokenBy
Indicates that one entity causes the damage, destruction, or loss of functionality of another entity.
-
C.
brokenOn
Indicates that an object or system ceased functioning or became damaged at a specific time or on a specific date.
-
D.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
E.
bondBroken
Indicates that a previously existing bond or connection between entities has been severed or is no longer intact.
- F. None of above. chosen
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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603452e3c8190a027cd2a9910c344 |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 22, 2026, 8:18 a.m.