Triple
T10293642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Arts |
E241426
|
entity |
| Predicate | hasLogoText |
P3623
|
FINISHED |
| Object | EA |
E855883
|
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: EA | Statement: [Electronic Arts, hasLogoText, EA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EA Context triple: [Electronic Arts, hasLogoText, EA]
-
A.
EA
EA was the IATA airline designator for Eastern Air Lines, a major U.S. carrier that operated primarily in the mid-20th century.
-
B.
EA
EA is the regional body responsible for delivering and overseeing education services across Northern Ireland.
-
C.
EA
chosen
EA is the stock ticker symbol for Electronic Arts, a major American video game company known for franchises like FIFA, Madden NFL, and The Sims.
-
D.
EA
EA is the commonly used abbreviation for the Environment Agency, the public body responsible for environmental protection and regulation in England.
-
E.
Ea
Ea, also known as Enki, is a major Mesopotamian god associated with wisdom, magic, and freshwater, revered as a creator and benefactor of humanity.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d46fb08190b7694290692e47dc |
completed | April 7, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7500fdd1c81909395469afb346f8b |
completed | April 9, 2026, 7:06 a.m. |
Created at: April 6, 2026, 11:42 a.m.