Triple
T2134394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresno Grizzlies |
E46615
|
entity |
| Predicate | formerClassLevel |
P8335
|
FINISHED |
| Object | Triple-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: Triple-A | Statement: [Fresno Grizzlies, formerClassLevel, Triple-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerClassLevel Context triple: [Fresno Grizzlies, formerClassLevel, Triple-A]
-
A.
classLevel
Indicates the academic or hierarchical level associated with a particular class within an educational or organizational structure.
-
B.
formerType
Indicates that one entity previously had a certain type, role, or classification but no longer does.
-
C.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
D.
predecessorClass
Indicates that one class precedes another in an ordered sequence or hierarchy, typically representing an earlier version or prior stage of that class.
-
E.
previousClassification
chosen
Indicates that one classification precedes another in time or in an ordered sequence of classifications.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba24004819091ffb9440e8615fa |
completed | March 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.