Triple
T23265309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amman Stock Exchange |
E588129
|
entity |
| Predicate | hasAcronym |
P43
|
FINISHED |
| Object | ASE |
—
|
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: ASE | Statement: [Amman Stock Exchange, hasAcronym, ASE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ASE Context triple: [Amman Stock Exchange, hasAcronym, ASE]
-
A.
ASE
ASE is a professional medical society dedicated to advancing cardiovascular ultrasound and improving patient care through education, research, and advocacy.
-
B.
ASE
chosen
ASE is the Amman Stock Exchange, the principal securities market of Jordan where stocks and other financial instruments are traded.
-
C.
ASE
ASE is the three-letter IATA airport code for Aspen–Pitkin County Airport, which serves the popular ski resort area of Aspen, Colorado.
-
D.
ASSE
ASSE is the commonly used abbreviation for AS Saint-Étienne, a historic French professional football club known for its success in Ligue 1.
-
E.
AS
AS is the two-letter IATA airline designator assigned to Alaska Airlines, used in flight numbers and ticketing.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cc3b908190aaefd036aa2b52b5 |
completed | April 29, 2026, 5:19 a.m. |
Created at: April 17, 2026, 4:34 p.m.