Triple
T5542481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldman Sachs |
E145322
|
entity |
| Predicate | tickerSymbol |
P1447
|
FINISHED |
| Object | GS |
E387202
|
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: GS | Statement: [Goldman Sachs, tickerSymbol, GS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GS Context triple: [Goldman Sachs, tickerSymbol, GS]
-
A.
GS
GS is the two-letter ISO 3166 country code assigned to the British Overseas Territory of South Georgia and the South Sandwich Islands in the southern Atlantic Ocean.
-
B.
GS
chosen
GS is the New York Stock Exchange ticker symbol for Goldman Sachs, a leading global investment banking, securities, and asset management firm.
-
C.
GS
GS is the vehicle registration code used on license plates for the town of Gospić in Croatia.
-
D.
GS
GS is the vehicle registration code used on license plates for the district of Goslar in Lower Saxony, Germany.
-
E.
GS
GS is the commonly used abbreviation for Google Scholar, a freely accessible web search engine that indexes scholarly literature across many disciplines and formats.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fc7e26481908cec8d0483170ea5 |
completed | March 22, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0281fb73881909df8e4f98b27ce1e |
completed | March 22, 2026, 5:34 p.m. |
Created at: March 22, 2026, 3:35 p.m.