Triple
T33206867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jose Giants |
E850035
|
entity |
| Predicate | hasLeagueClassification |
P154807
|
FINISHED |
| Object | Single-A |
—
|
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 | Statement: [San Jose Giants, hasLeagueClassification, Single-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeagueClassification Context triple: [San Jose Giants, hasLeagueClassification, Single-A]
-
A.
hasTeamClassification
Indicates that an entity is assigned a specific team-based category or classification.
-
B.
hasSportClassification
chosen
Indicates that an entity is assigned a specific category or class within a sports-related system or framework.
-
C.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
D.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
-
E.
hasSeparateLeagueSystemFor
Indicates that one entity organizes or maintains a distinct, independent league structure specifically for another entity or group.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 1:30 a.m.