Triple
T7170230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inland Empire 66ers of San Bernardino |
E167174
|
entity |
| Predicate | reclassifiedTo |
P22031
|
FINISHED |
| Object | Single-A in 2021 |
—
|
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: Single-A in 2021 | Statement: [Inland Empire 66ers of San Bernardino, reclassifiedTo, Single-A in 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reclassifiedTo Context triple: [Inland Empire 66ers of San Bernardino, reclassifiedTo, Single-A in 2021]
-
A.
reclassifiedAs
chosen
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
B.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
C.
reconvertedTo
Indicates that something has been changed back or restored to a previous state, form, or condition it once had.
-
D.
reclassificationYear
Indicates the year in which something was reassigned to a different category, status, or classification.
-
E.
recastBy
Indicates that an existing role, character, or part has been newly assigned to a different performer or entity than before.
- F. None of above.
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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85d8f208190915f6f4c05988b63 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1ce5f048190808c378a980f7bb6 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.