Triple
T6387243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAAPM |
E143730
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | FAAPM |
E143730
|
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: FAAPM | Statement: [FAAPM, hasAbbreviation, FAAPM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FAAPM Context triple: [FAAPM, hasAbbreviation, FAAPM]
-
A.
FAAPM
chosen
FAAPM is a professional designation awarded to distinguished members of the American Association of Physicists in Medicine in recognition of significant contributions to the field of medical physics.
-
B.
FPM
FPM is the Fellow Programme in Management, a doctoral-level research program in management studies offered by the Indian Institutes of Management.
-
C.
EFPM
EFPM is the Executive Fellow Programme in Management, a doctoral-level program designed for working professionals to pursue advanced research in management.
-
D.
FAP
FAP is the acronym for the Peruvian Air Force, the aerial warfare branch of Peru’s armed forces.
-
E.
FAP
FAP is the acronym for the Portuguese Air Force, the aerial warfare branch of Portugal’s Armed Forces.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06869dfb88190aeb84c6c61414888 |
completed | March 22, 2026, 10:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6387dc8888190ba63efcc9aff41b2 |
completed | March 27, 2026, 7:57 a.m. |
Created at: March 22, 2026, 4:34 p.m.