Triple
T32017530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDY |
E817584
|
entity |
| Predicate | foundedAsTicker |
P23749
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [TDY, foundedAsTicker, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsTicker Context triple: [TDY, foundedAsTicker, 1999]
-
A.
formerTickerSymbol
chosen
Indicates that one entity was previously used as the stock ticker symbol for another entity, but is no longer its current ticker symbol.
-
B.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
C.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
-
D.
hasCorporateTickerRoot
Indicates that a company’s stock ticker symbol is derived from or based on the specified root string.
-
E.
issuerFoundedAs
Indicates that the issuer was originally established or created under a particular prior name, form, or organizational identity.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 12:16 a.m.