Triple
T5433057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siebel Systems |
E121541
|
entity |
| Predicate | stockTicker |
P1447
|
FINISHED |
| Object | SEBL |
E121541
|
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: SEBL | Statement: [Siebel Systems, stockTicker, SEBL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SEBL Context triple: [Siebel Systems, stockTicker, SEBL]
-
A.
SEBL
chosen
SEBL was the stock ticker symbol for Siebel Systems, a prominent customer relationship management (CRM) software company later acquired by Oracle.
-
B.
SEB
SEB is the IATA airport code for Sabha Airport, which serves the city of Sabha in southwestern Libya.
-
C.
SEMAL
SEMAL is the UN/LOCODE designation for the port and transport location associated with Lake Mälaren in Sweden.
-
D.
SEREB
SEREB was a French aerospace company involved in the development of ballistic missiles and space launch vehicles before being merged into Aérospatiale.
-
E.
Sel
Sel is a municipality in Innlandet county, Norway, known for its mountainous landscapes and location in the Gudbrandsdalen valley.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd91ae18cc8190aefe610f91b5382c |
completed | March 20, 2026, 6:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf3accb6748190989257c3b991a760 |
completed | March 22, 2026, 12:41 a.m. |
Created at: March 20, 2026, 2:06 p.m.