Triple
T2928257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ThunderDome |
E78896
|
entity |
| Predicate | primaryUseAfterRenaming |
P5014
|
FINISHED |
| Object | baseball |
—
|
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: baseball | Statement: [ThunderDome, primaryUseAfterRenaming, baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseAfterRenaming Context triple: [ThunderDome, primaryUseAfterRenaming, baseball]
-
A.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
B.
useAfterRenovation
Indicates that something is intended to be used or occupied only after renovation work has been completed.
-
C.
subsequentUse
chosen
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
D.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
E.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97ff0ddc8190acba9863bbe4f54b |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.