Triple
T22253547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L3Harris Technologies, Inc. |
E550039
|
entity |
| Predicate | tradesUnderSymbol |
P35294
|
FINISHED |
| Object | LHX |
—
|
NE NERFINISHED |
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: LHX | Statement: [L3Harris Technologies, Inc., tradesUnderSymbol, LHX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LHX Context triple: [L3Harris Technologies, Inc., tradesUnderSymbol, LHX]
-
A.
LHX
chosen
LHX is the stock ticker symbol for L3Harris Technologies, a major American defense and aerospace technology company.
-
B.
LHX
LHX is the FAA location identifier for La Junta Municipal Airport in Colorado, United States.
-
C.
LHZ
LHZ is the IATA airport code for Triangle North Executive Airport, a public airport serving the Louisburg, North Carolina area.
-
D.
HLX
HLX is the ICAO airline designator for Hapag-Lloyd Express, a former German low-cost carrier.
-
E.
LTX
LTX is the IATA airport code for Cotopaxi International Airport serving Latacunga, Ecuador.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c0c4f48190a75473a7835014f1 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 16, 2026, 8:39 p.m.