Triple
T7828200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football Association of Malaysia |
E181298
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | FAM |
E695331
|
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: FAM | Statement: [Football Association of Malaysia, abbreviation, FAM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FAM Context triple: [Football Association of Malaysia, abbreviation, FAM]
-
A.
FAM
FAM is the acronym commonly used to refer to the Mexican Air Force, the aerial warfare branch of Mexico’s armed forces.
-
B.
FAM
chosen
FAM is the national governing body responsible for overseeing and developing football in Malaysia.
-
C.
FAMO
FAMO was a German vehicle manufacturer best known for producing military half-tracks and armored vehicles for the Wehrmacht during World War II.
-
D.
FAM AB
FAM AB is a Swedish investment company that manages and develops long-term holdings on behalf of the Wallenberg family.
-
E.
FAMa
FAMa is the national military force of Mali responsible for the country’s defense and security operations.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04a97d748190b1924890b1328bf1 |
completed | March 30, 2026, 11:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5a797ee881908068ba7346042756 |
completed | March 31, 2026, 5:24 a.m. |
Created at: March 30, 2026, 4:43 p.m.