Triple
T17077930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equifax Inc. |
E414396
|
entity |
| Predicate | tickerSymbol |
P1447
|
FINISHED |
| Object | EFX |
E85145
|
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: EFX | Statement: [Equifax Inc., tickerSymbol, EFX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EFX Context triple: [Equifax Inc., tickerSymbol, EFX]
-
A.
EFX
chosen
EFX is the stock ticker symbol for Equifax Inc., a major U.S.-based consumer credit reporting agency.
-
B.
Special EFX
Special EFX is a contemporary jazz fusion group known for blending smooth jazz, world music, and Latin influences into melodic, groove-oriented compositions.
-
C.
FEF
FEF is the commonly used abbreviation for the Ecuadorian Football Federation, the governing body of football in Ecuador.
-
D.
EF
EF is the commonly used abbreviation for the Eclipse Foundation, a nonprofit organization that oversees open-source software projects and the Eclipse IDE ecosystem.
-
E.
EF
EF is the vehicle registration code used on license plates for the German city of Erfurt.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc625c48190b679a521180e10ad |
completed | April 18, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012edfda588190aff6c6d4c8d64ddd |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:34 a.m.