Triple
T16279624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston RiverDogs |
E395229
|
entity |
| Predicate | formerlyClassLevel |
P8335
|
FINISHED |
| Object | Class 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: Class A | Statement: [Charleston RiverDogs, formerlyClassLevel, Class A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyClassLevel Context triple: [Charleston RiverDogs, formerlyClassLevel, Class A]
-
A.
classLevel
Indicates the academic or hierarchical level associated with a particular class within an educational or organizational structure.
-
B.
previousClassification
chosen
Indicates that one classification precedes another in time or in an ordered sequence of classifications.
-
C.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
D.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
E.
clase
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by another entity.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24610908c8190921e507dcb4d8250 |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.