Triple
T10625299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firearm Owners Protection Act |
E250306
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | FOPA |
E250306
|
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: FOPA | Statement: [Firearm Owners Protection Act, alsoKnownAs, FOPA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FOPA Context triple: [Firearm Owners Protection Act, alsoKnownAs, FOPA]
-
A.
FOPA
chosen
FOPA is a U.S. federal law enacted in 1986 that revised and expanded regulations on the sale, ownership, and transportation of firearms.
-
B.
FPO
FPO is the IATA airport code for Grand Bahama International Airport, serving Freeport in the Bahamas.
-
C.
FPO
FPO is the commonly used abbreviation for the Orinoco Petroleum Belt, a vast oil-rich region in Venezuela containing some of the world’s largest extra-heavy crude reserves.
-
D.
FACA
FACA is the commonly used acronym for the Federal Advisory Committee Act, a U.S. law that governs the operation and transparency of federal advisory committees.
-
E.
FAP
FAP is the acronym for the Peruvian Air Force, the aerial warfare branch of Peru’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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df80a30c81909f36fe221cf68822 |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d96b9a27f881908e451bfa6c118af4 |
completed | April 10, 2026, 9:28 p.m. |
Created at: April 8, 2026, 8:54 p.m.