Triple
T443194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durham Bulls |
E10157
|
entity |
| Predicate | previousClassLevel |
P10130
|
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: [Durham Bulls, previousClassLevel, Class A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousClassLevel Context triple: [Durham Bulls, previousClassLevel, Class A]
-
A.
previousClassification
Indicates that one classification precedes another in time or in an ordered sequence of classifications.
-
B.
classLevel
Indicates the academic or hierarchical level associated with a particular class within an educational or organizational structure.
-
C.
predecessorClass
chosen
Indicates that one class precedes another in an ordered sequence or hierarchy, typically representing an earlier version or prior stage of that class.
-
D.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
E.
previousTitle
Indicates that one title held or used by an entity directly preceded another title in sequence or time.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef43e8f88190a5d368add11a38c0 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.