Triple
T14802027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne Storm |
E347930
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | MEL |
E158312
|
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: MEL | Statement: [Melbourne Storm, abbreviation, MEL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MEL Context triple: [Melbourne Storm, abbreviation, MEL]
-
A.
MEL
chosen
MEL is the three-letter IATA airport code for Melbourne Airport, the primary international gateway serving Melbourne, Australia.
-
B.
Mello
Mello is the official mascot character created for the 2007 ICC Cricket World Cup held in the West Indies.
-
C.
MEG
MEG is the stock ticker symbol of Megaworld Corporation, a major Philippine real estate developer known for its large-scale township projects.
-
D.
mello
mello is a digital-first mortgage and lending platform developed by loanDepot to streamline and modernize the home loan experience.
-
E.
Mel
Mel is a common shortened form of the given name Melissa, often used as a casual or affectionate nickname.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf30d044819082ac038e06481aab |
completed | April 14, 2026, 11:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24c4f690819087504fcfd2df8ba3 |
completed | May 8, 2026, 6 p.m. |
Created at: April 10, 2026, 1:31 a.m.