Triple
T35916123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twilio Inc. |
E1038753
|
entity |
| Predicate | ipoTicker |
P1447
|
FINISHED |
| Object | TWLO |
—
|
NE NERFINISHED |
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: TWLO | Statement: [Twilio Inc., ipoTicker, TWLO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ipoTicker Context triple: [Twilio Inc., ipoTicker, TWLO]
-
A.
tickerSymbol
chosen
Indicates the association between a financial instrument or company and its unique abbreviated code used for trading on a securities exchange.
-
B.
tickerFor
Indicates that one entity is the stock ticker symbol used to uniquely identify another entity (typically a publicly traded company or security) in financial markets.
-
C.
hasExchangeTicker
Indicates that an entity is identified or listed under a specific ticker symbol on a particular financial exchange.
-
D.
issuerMarket
Indicates a relationship where a specific market is associated with, or serves as the trading or listing venue for, a given issuer.
-
E.
exchangeTickerFormat
Indicates the specific formatting convention used to represent a security’s ticker symbol on a particular exchange.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaa69e2c8190aad5087427023959 |
completed | May 3, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.