Triple
T32551549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnstown Tomahawks |
E831986
|
entity |
| Predicate | juniorTier |
P174522
|
FINISHED |
| Object | Tier II |
—
|
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: Tier II | Statement: [Johnstown Tomahawks, juniorTier, Tier II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: juniorTier Context triple: [Johnstown Tomahawks, juniorTier, Tier II]
-
A.
junior
chosen
Indicates that one entity holds a lower rank, status, or level of experience relative to another within a shared context.
-
B.
youthTier
Indicates a classification relationship where an entity is assigned to a specific youth-related level, category, or bracket within a tiered system.
-
C.
juniorLevelEvent
Indicates that an event is classified as being at a junior or entry level in terms of required experience or seniority.
-
D.
traditionalTier
Indicates that an entity belongs to, or is categorized within, a conventional or historically established level, class, or rank in a tiered system.
-
E.
juniorPartner
Indicates that one entity holds a subordinate or less senior partnership role in relation to another entity within a shared partnership.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:02 a.m.