Triple
T25888661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major League Baseball color barrier |
E652263
|
entity |
| Predicate | maintainedUntil |
P160696
|
FINISHED |
| Object | 1947 |
—
|
LITERAL 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: 1947 | Statement: [Major League Baseball color barrier, maintainedUntil, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedUntil Context triple: [Major League Baseball color barrier, maintainedUntil, 1947]
-
A.
maintainedFor
Indicates that something is kept in a particular state, condition, or operation for the benefit, use, or purpose of another entity.
-
B.
maintainedSince
Indicates that an entity has been kept in a particular state or condition continuously from a specified point in time onward.
-
C.
maintainedDuring
Indicates that a certain condition, state, or relationship continues to hold throughout the duration of a specified event or time interval.
-
D.
maintainedAt
Indicates that an entity is kept in proper working order, condition, or status at a particular place, time, or context.
-
E.
managedUntil
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
- 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_69f60459a53c8190bbd90e80890eebcd |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f603b90c94819088d62cb9489e95ff |
completed | May 2, 2026, 2:01 p.m. |
Created at: April 22, 2026, 8:18 a.m.