Triple
T8839128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodrich Corporation |
E210341
|
entity |
| Predicate | tickerSymbol |
P1447
|
FINISHED |
| Object | GR |
E210341
|
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: GR | Statement: [Goodrich Corporation, tickerSymbol, GR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GR Context triple: [Goodrich Corporation, tickerSymbol, GR]
-
A.
GR
GR is the standard abbreviation for Georgian Railway, the national rail transport company of Georgia.
-
B.
GR
chosen
GR is the stock ticker symbol for Goodrich Corporation, a former major American aerospace and defense company known for manufacturing aircraft systems and components.
-
C.
GR
GR is the performance and motorsport sub-brand of Toyota, known for developing high-performance road cars and competing in international racing series.
-
D.
GRA
GRA is the ring-shaped orbital motorway encircling Rome, Italy, serving as a major traffic artery for the metropolitan area.
-
E.
GU
GU is a United Kingdom postcode area covering Guildford and surrounding parts of Surrey and nearby counties.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60849f8c8190b7735defecf55a5d |
completed | April 1, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf89933e8c81909672bcec70f7d5ce |
completed | April 3, 2026, 9:34 a.m. |
Created at: March 30, 2026, 6:48 p.m.