Triple
T6274420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block, Inc. |
E140619
|
entity |
| Predicate | tickerSymbol |
P1447
|
FINISHED |
| Object | SQ |
E579507
|
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: SQ | Statement: [Block, Inc., tickerSymbol, SQ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SQ Context triple: [Block, Inc., tickerSymbol, SQ]
-
A.
SQ
SQ is the commonly used abbreviation for Stadiums Queensland, the government agency responsible for managing major sports and entertainment venues in Queensland, Australia.
-
B.
SQ
chosen
SQ is the stock ticker symbol for Block, Inc. (formerly Square, Inc.), a major American financial technology company known for its payment processing and digital financial services.
-
C.
SQ
SQ is the IATA airline designator used worldwide to identify Singapore Airlines on tickets, timetables, and flight numbers.
-
D.
SQ3
SQ3 is a designated quadrant within the Southern Cross region, used for organizing and referencing a specific area of the sky.
-
E.
QR
QR is the two-letter IATA airline designator assigned to Qatar Airways, the flag carrier of Qatar.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063c0629c8190805ddf1a604e9ca4 |
completed | March 22, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c519404dbc8190850f7874d2be51b5 |
completed | March 26, 2026, 11:32 a.m. |
Created at: March 22, 2026, 4:25 p.m.