Triple
T34059381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wildcat Ruckus |
E873448
|
entity |
| Predicate | associatedAcronym |
P205297
|
FINISHED |
| Object | SEC |
E7145
|
NE 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: SEC | Statement: [The Wildcat Ruckus, associatedAcronym, SEC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAcronym Context triple: [The Wildcat Ruckus, associatedAcronym, SEC]
-
A.
acronymContext
Indicates that one term is used as an acronym specifically within the contextual scope defined by another entity (such as a document, domain, or usage setting).
-
B.
acronymExpansion
Indicates that one term is an acronym whose letters stand for the words in another, longer expression.
-
C.
relatedAbbreviationSystem
Indicates that one entity is associated with, or belongs to, a particular system of abbreviations used to represent it.
-
D.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
E.
abbreviationUsedBy
Indicates that a particular abbreviation is employed or adopted by a specified entity in its communication, documentation, or usage.
- F. None of above. chosen
Provenance (5 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36a046766c8190b6509281dcb2c85b |
completed | June 20, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:52 a.m.