Triple
T14264852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xerox Holdings Corporation |
E353618
|
entity |
| Predicate | hasTickerSymbol |
P1447
|
FINISHED |
| Object | XRX |
E353618
|
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: XRX | Statement: [Xerox Holdings Corporation, hasTickerSymbol, XRX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XRX Context triple: [Xerox Holdings Corporation, hasTickerSymbol, XRX]
-
A.
XRX
chosen
XRX is the stock ticker symbol for Xerox Holdings Corporation, an American company known for its document management technologies and printing solutions.
-
B.
XKRX
XKRX is the Market Identifier Code (MIC) for the Korea Exchange, South Korea’s main securities and derivatives marketplace.
-
C.
XRY
XRY is the IATA airport code for Jerez Airport, an international airport serving Jerez de la Frontera and the surrounding Cádiz region in southern Spain.
-
D.
RXA
RXA is the ICAO airline designator assigned to Rex Airlines, an Australian regional carrier.
-
E.
XCR
XCR is the IATA airport code for Châlons Vatry Airport in northeastern France, which serves the Champagne region and cargo operations.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6357a8188190ba518a486521052b |
completed | April 14, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd326367348190b4b31b32f4ca5639 |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:09 a.m.